Hi gazoox22, I am sorry for this inconvenience. All the boards sustain testing phases to check 100% they are functional before shipment. I have personally had only two cases out of thousands of boards where after positive testing of the board, during manipulation activities before the final test a small metallic powder bit insinuates itself between two pins of the Flash memory on the bottom of the Fox. The short circuit between those pins prevented the board to boot and prevented any erasing sector operation. In both cases I had the small metallic impurity above the printed circuit board but between the first pins of the Flash memory chip (between pin 1 and pin 10). Try to see if you are able to spot it in case this is the problem. If you find it, you can try with a thin tool to remove it. If you find it but you are not sure about how to remove it or don't feel confident, don't worry. Try to take a picture of the particular detail and send it to us. If we don't manage to get it working we will replace the board.
Meanwhile please report the complete description printed on the Flash and SDRAM memory chip of your board. Look here to see how the FLASH and SDRAM memory chips looks like: http://www.acmesystems.it/?id=832 On the flashing side, I see on the second listing, that you have altered the partition sizes so that the sum of the partition sizes is over the 0x400000 value. So the message of Flash too small ... This is wrong. You should try to flash your board with the fimage produced by your environment by default just after installation before trying to experiment with partition sizes. I suggest you to reinstall the SDK, since it is very difficult to help fixing wrong settings on the SDK once have benn changed lots of options. Anyway please try to flash the board with one of the images we provide on our website: http://www.acmesystems.it/?id=704 like this one: http://www.acmesystems.it/articles/00704/fimage221106.zip and report your advances. Sorry again for this inconvenience. Bestregards, Roberto Asquini gazoox22 ha scritto: > > Hi all. > > Two days ago I recieved my FoxBoard LX. The first tests faild, nothing > worked. Only the green LED was on all the time with no network activity. > Well, trying to flash the board causes errors. I tried two network > cards, a few power supplies, but nothing helped. > > a "./boot_linux -F" gives the message: > > [EMAIL PROTECTED] devboard-R2_01]# ./boot_linux -F > Prepending "/home/gazoox/fox/devboard-R2_01/tools/build/bin" to PATH. > Prepending "/usr/local/cris/bin" to PATH. > Using internal boot loader: INTERNAL_NW - Network boot (default). > Starting boot... > We're doing a flash write, this may take up to a few minutes... > > Device ID = 0x00006137 > This bootloader was built by gazoox on Fr 2. Feb 01:54:20 CET 2007. > Checksum of bootloader is 0x000a0a8c > Waiting for load info. > Checksum of file is 0x00001e3d > Got load info. > SET_REGISTER > 0xb0000000 > 0x000095f8 > SET_REGISTER > 0xb0000004 > 0x00000004 > SET_REGISTER > 0xb000000c > 0x09603636 > SET_REGISTER > 0xb0000008 > 0x8000c002 > PAUSE_LOOP > 0x00020000 > SET_REGISTER > 0xb0000008 > 0x8000c602 > SET_REGISTER > 0xb0000008 > 0x8000c002 > SET_REGISTER > 0x38001f00 > 0x00000007 > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8000c402 > SET_REGISTER > 0xb0000008 > 0x8000c002 > LOOP > 0x38001f00 > 0x38001f5c > SET_REGISTER > 0xb0000008 > 0x8030c202 > SET_REGISTER > 0xb0000008 > 0x8000c002 > SET_REGISTER > 0xb0000008 > 0x80008002 > SET_REGISTER > 0xb0000030 > 0x00001df0 > SET_REGISTER > 0xb0000038 > 0x0000ce03 > PACKET_INFO > 0xc0004000 > 0x00400018 > Checksum of file is 0x299fc3b5 > FLASH > 0xc0004000 > 0x00000000 > 0x00400000 > Found 1 x CFI at 0x80000000 > No single x16 at 0x84000000 > No interleaved x16 at 0x84000000 > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > 0x80000000: Erasing 0x00313100 bytes > Sector erase error > END > Exiting with code 0 > > ------------------------------------------- > > and sometimes the board tries to erase the flash: > > [...] > Checksum of file is 0x299fc3b5 > FLASH > 0xc0014000 > 0x00010000 > 0x003f0000 > Found 1 x CFI at 0x80000000 > No single x16 at 0x84000000 > No interleaved x16 at 0x84000000 > Fatal: flash is too small. > END > Exiting with code 0 > [EMAIL PROTECTED] devboard-R2_01]# > > ------------------------------- > > I'm tring to solve the problem much too many hours until now. Please > help! :-< [:-/] > > [Non-text portions of this message have been removed] > > -- Roberto Asquini Acme Systems srl [EMAIL PROTECTED] http://www.acmesystems.it
