Re: about JFlash

From: SPINELLI Olivier (spinelliolivier_at_yahoo.fr)
Date: 04/30/04


Date: 30 Apr 2004 01:10:37 -0700

Hello,

you need to erase the flash before writing.

Olivier

"Lilo" <zheye@moons.com.cn> wrote in message news:<OEQq4xlLEHA.2400@tk2msftngp13.phx.gbl>...
> ? Hi,all:
>
> Form the messages shows below,what can tell me?Has one of the Flash
> crashed or other?
> but "read Q,read R and read Y" run well.what should I do?
> JFLASH Version 2.10.002 - DBPXA250
> COPYRIGHT (C) 2000-2002 Intel Corporation
> PXA250 revision 0x6??
>
> attr: 00510051
> There are two 16-bit Flash devices in parallel
>
> Characteristics for one device:
> Number of blocks in device = 128
> Block size = 65536 0x10000 word(16-bit)
> Device size = 8388608 0x800000 word(16-bit)
>
> Sample block to address list:
>
> Block 0 = hex address: 00000000
> Block 40 = hex address: 00A00000
> Block 80 = hex address: 01400000
> Block 120 = hex address: 01E00000
> The last 66 percent of image file is all zeros
> Would you like to save time by not programming that area? [y/n]:
> Starting erase
> Erasing block 0
> Erasing done
> Starting programming
> Writing flash at hex address 1000, 1.56% done
> Writing flash at hex address 2100, 3.22% done
> Writing flash at hex address 2f80, 4.64% done
> Writing flash at hex address 4080, 6.30% done
> Writing flash at hex address 4f80, 7.76% done
> Writing flash at hex address 5f80, 9.33% done
> Writing flash at hex address 7100, 11.04% done
> Writing flash at hex address 8240, 12.72% done
> Writing flash at hex address 9180, 14.21% done
> Writing flash at hex address a300, 15.92% done
> Writing flash at hex address b440, 17.60% done
> Writing flash at hex address c5c0, 19.31% done
> Writing flash at hex address d740, 21.02% done
> Writing flash at hex address e8c0, 22.73% done
> Writing flash at hex address fa40, 24.44% done
> Writing flash at hex address 10bc0, 26.15% done
> Writing flash at hex address 11d80, 27.88% done
> Writing flash at hex address 12f00, 29.59% done
> Writing flash at hex address 14080, 31.30% done
> Writing flash at hex address 15200, 33.01% done
> Writing flash at hex address 16380, 34.72% done
> Writing flash at hex address 17500, 36.43% done
> Writing flash at hex address 18680, 38.13% done
> Writing flash at hex address 19840, 39.87% done
> Writing flash at hex address 1a9c0, 41.58% done
> Writing flash at hex address 1bb40, 43.29% done
> Writing flash at hex address 1ccc0, 45.00% done
> Writing flash at hex address 1de40, 46.70% done
> Writing flash at hex address 1efc0, 48.41% done
> Writing flash at hex address 20140, 50.12% done
> Writing flash at hex address 212c0, 51.83% done
> Writing flash at hex address 22400, 53.52% done
> Writing flash at hex address 23580, 55.22% done
> Writing flash at hex address 24700, 56.93% done
> Writing flash at hex address 25880, 58.64% done
> Writing flash at hex address 26a00, 60.35% done
> Writing flash at hex address 27b80, 62.06% done
> Writing flash at hex address 28d00, 63.77% done
> Writing flash at hex address 29e80, 65.48% done
> Writing flash at hex address 2b000, 67.19% done
> Writing flash at hex address 2c1c0, 68.92% done
> Writing flash at hex address 2d300, 70.61% done
> Writing flash at hex address 2e4c0, 72.34% done
> Writing flash at hex address 2f640, 74.05% done
> Writing flash at hex address 307c0, 75.76% done
> Writing flash at hex address 31940, 77.47% done
> Writing flash at hex address 32ac0, 79.17% done
> Writing flash at hex address 33c40, 80.88% done
> Writing flash at hex address 34dc0, 82.59% done
> Writing flash at hex address 35f40, 84.30% done
> Writing flash at hex address 37080, 85.99% done
> Writing flash at hex address 38200, 87.70% done
> Writing flash at hex address 39380, 89.40% done
> Writing flash at hex address 3a500, 91.11% done
> Writing flash at hex address 3b680, 92.82% done
> Writing flash at hex address 3c7c0, 94.51% done
> Writing flash at hex address 3d940, 96.22% done
> Writing flash at hex address 3eac0, 97.92% done
> Writing flash at hex address 3fc40, 99.63% done
> Programming done
> Starting Verify
> verify error at address = 0 exp dat = ea0003fe act dat = ea003fff
> verify error at address = 1 exp dat = 0 act dat = 3ff9
> verify error at address = 2 exp dat = 0 act dat = 3ff9
> verify error at address = 3 exp dat = 0 act dat = 3ff9
> verify error at address = 4 exp dat = 0 act dat = 3ff9
>
>
>
>
>
> --



Relevant Pages

  • Re: What is preferable for storing parameters FLASH or on-chip EEPROM ?
    ... > It has 2k EEPROM on-chip and 64kB Flash. ... > 2) Supports only Byte programming. ... > programming Flash to not erase the log area. ...
    (comp.arch.embedded)
  • Re: Bootloader - erase flash memory
    ... Erasing flash means setting every bit to 1. ... So, to write your firmware into the flash, you have to first erase the ... most flash chips need a special programming ...
    (comp.arch.embedded)
  • Re: o_sync in vfat driver
    ... flash disks are not stupid as you assume. ... It takes about a second to erase a 64k physical sector. ... device eth0 entered promiscuous mode ... movb $0xaa, 0x555 ...
    (Linux-Kernel)
  • Re: 8051: writing to memory in the program
    ... Non-volatile memory. ... (typically FLASH or EEPROM, ... Interrupts need to be disabled while programming if there are ISRs ... This problem disappears, of course, if you have both FLASH and EEPROM ...
    (comp.arch.embedded)
  • OT: Remote On Chip Debugging
    ... Currently you have to use one of the programming suites for that. ... So you have customers that reject any flash based designs? ... programming an ARM Cortex M3 using remote gdb server on the targets. ... example, Flash Address Register, Flash Data Register, ...
    (sci.electronics.design)