Archived Boards and Threads > Eddy Modules

Eddy v2.5 don't work (serialflash missing)

(1/2) > >>

Dear all:

Today I had working 2 eddy CPU modules S/N:EC102xxxxx over the eddy DKv2.1 (it worked ok).
Well, when I changed the jumper of FPG input and try to use SAMBA the eddy don't recognize serialflash, .

There are a patch of SAMBA in download section, and other SAMBA files.
I have other eddy CPU module S/N:EB530xxxxx that works fine with SAMBA.
What version of eddy works fine with SAMBA versions? ( the Serialflash IC mounted in the eddy is different between versions)
How could I recovery both eddy modules?

I show the log of SAMBA below:
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.10  on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : \usb\ARM0
-I- argv 1 : AT91SAM9G20-EK
-I- argv 2 : Eddy_burning_SerialFlash.tcl
-I- Connection : \usb\ARM0 (target(comType) = 0)
-I- Board : at91sam9g20-ek
-I- Traces Level : 4
-I- target(handle) : 18345656
Read device Chip ID at 0xfffff240 --- get 0x019905a1
-I- Found processor : at91sam9g20 (Chip ID : 0x019905a1)
-I- External RAM Settings :  extRamVdd=1, extRamType=0, extRamDataBusWidth=16, extDDRamModel=0
-I- Loading applet isp-extram-at91sam9g20.bin at address 0x200000
-I- Memory Size : 0x4000000 bytes
-I- Buffer address : 0x2013AC
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- External RAM initialized
-I- Command line mode : Execute script file : Eddy_burning_SerialFlash.tcl
u-boot file: eddy-bl-
filesystemSize: 0x002A82D0
-I- === Performs sanity checks===
-I- === Initialize the SerialFlash access ===
-I- SERIALFLASH::Init 1 (trace level : 4)
-I- Loading applet isp-serialflash-at91sam9g20.bin at address 0x20000000
-E- Script File Eddy_burning_SerialFlash.tcl returned error : Can't detect known device - Can't detect known device
    while executing
"error "Can't detect known device""
    (procedure "GENERIC::Init" line 45)
    invoked from within
"GENERIC::Init $SERIALFLASH::appletAddr $SERIALFLASH::appletMailboxAddr $SERIALFLASH::appletFileName [list $target(comType) $target(traceLevel) $sfId]"
    (procedure "SERIALFLASH::Init" line 10)
    invoked from within
    (file "Eddy_burning_SerialFlash.tcl" line 136)
    invoked from within
"source $scriptFile"

Can anybody help me?

thanks in advance


Hi moisnico,

I am not aware that there are problems with different serial numbers (I will test it). Normally, the v2.5 Modules could be programmed over sam-ba 2.10.
Did you follow the instructions in "Eddy-DK Programmer Guide (2011.01.20)"  "9.1.2 Hardware Install and Recovery"?

yes, I followed the instructions.

I had doubts about the eddy_cpu update process, and because this, I tested with 2 modules of different S/N.

Perhaps, there are any interaction between SAMBA and UBOOT. ( I think that they are independent). What do you think about this?

I wish write the external NAND flash with the same linux image, and try to run the eddy from this location. Could you help me?


Thorsten Trenz:
we discussed the problem with SystemBase, and they requested a photo of each module. Can you please provide it?
The serial flash chip should be visible on the photo.

best regards
Thorsten Trenz

Antti Lukats:

1) if SAM-BA is activated and sees the eddy module then related working items are
- clock
- reset
- cpu (internal ROM-RAM)
- usb connection

samba will work, not matter the external ram or flash availability..

2) eddy board has a special pin that DISABLES the spi flash, it is some nand gate.. when its disabled then the spi flash NOT ACCESSIBLE, it would read 0xFFFFFFF as flash ID, causing of the samba flash applet to not recognize the chip

3) eddy board (at least some versions?) use a spi flash that is not supported by the atmel original spi flash applet, so special version must be used, it is one small BIN file that is fetched from samba support folders, if this file is OLD then samba would get chip not recognized error during spi applet init

We do not know, but it could be that some eddy modules have spi flash that is directly supported with atmel original spi applet binary, if that is the case, then your samba may fetch old (not sysbas supplied) spi applet, that would have the behaviour as you see, one sn work, other fails.

so, PLEASE make sure the update scripts loads MODIFIED spi applet bin file!

We have made a patched version of samba applets that allow us to use samba GUI to talk to the eddy, load ram, flash spi.. if you can not get working, we can upload our patched version

Antti Lukats


[0] Message Index

[#] Next page

Go to full version