Main Site Documentation

I think I broke the previous Installer thread


#1

It seems that my last post freaked out the thread about the new Hydra SDK. The log file I posted was apparently too much for it to handle :frowning: Going to try again here except eliminating a lot of the “erasing…” entries.

The log appears to me that the firmware update works. However, when I do a ping it is coming back as TinyBooter instead of TinyCLR. Ideas?


-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA CDC 2.10  on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : com12
-I- argv 1 : at91sam9rl64-ek
-I- argv 2 : TinyBooterLoader.tcl
-I- Connection : com12 (target(comType) = 3)
-I- Board : at91sam9rl64-ek
-I- Traces Level : 4
-I- target(handle) : file22168c8
Read device Chip ID at 0xfffff240 --- get 0x019b03a0
-I- Found processor : at91sam9rl64 (Chip ID : 0x019b03a0)
-I- Command line mode : Execute script file : TinyBooterLoader.tcl
-I---------------------------------
-I-   GHI Electronics, FEZ Hydra  -
-I-   TinyBooter Updater Script   -
-I---------------------------------
-I Enable DataFlash
-I- DATAFLASH::Init 0 (trace level : 4)
-I- Loading applet isp-dataflash-fez_hydra.bin at address 0x300000
-I- Memory Size : 0x420000 bytes
-I- Buffer address : 0x302CD8
-I- Buffer size: 0x18C0 bytes
-I- Applet initialization done
-I Erasing DataFlash
-I- 	Erasing: 0x18C0 bytes at address 0x0
-I- 	Erasing: 0x18C0 bytes at address 0x18C0
....
-I- 	Erasing: 0x18C0 bytes at address 0x41D6C0
-I- 	Erasing: 0x18C0 bytes at address 0x41EF80
-I- Send File FEZ_HYDRA_TINYBOOTER.bin at address 0x8400
GENERIC::SendFile FEZ_HYDRA_TINYBOOTER.bin at address 0x8400
-I- File size : 0xEAC4 byte(s)
-I- 	Writing: 0x18C0 bytes at 0x8400 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0x9CC0 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0xB580 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0xCE40 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0xE700 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0xFFC0 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0x11880 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0x13140 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0x18C0 bytes at 0x14A00 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0xC04 bytes at 0x162C0 (buffer addr : 0x302CD8)
-I- 	0xC04 bytes written by applet
-I- Temp file : C:/Users/Ian/.sam-ba.testCompareFile
-I- Compare File : FEZ_HYDRA_TINYBOOTER.bin with memory at address : 0x8400 , for 60100 byte(s)
-I- Read File C:/Users/Ian/.sam-ba.testCompareFile at address 0x8400
GENERIC::ReceiveFile C:/Users/Ian/.sam-ba.testCompareFile : 0xEAC4 bytes from address 0x8400
-I- 	Reading: 0x18C0 bytes at 0x8400 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0x9CC0 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0xB580 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0xCE40 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0xE700 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0xFFC0 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0x11880 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0x13140 (buffer addr : 0x302CD8)
-I- 	Reading: 0x18C0 bytes at 0x14A00 (buffer addr : 0x302CD8)
-I- 	Reading: 0xC04 bytes at 0x162C0 (buffer addr : 0x302CD8)
Sent file & Memory area content (address: 0x8400, size: 60100 bytes) match exactly !
GENERIC::SendFile GHI_OSH_BOOTSTRAP.bin at address 0x0
-I- File size : 0x25E8 byte(s)
-I- 	Writing: 0x18C0 bytes at 0x0 (buffer addr : 0x302CD8)
-I- 	0x18C0 bytes written by applet
-I- 	Writing: 0xD28 bytes at 0x18C0 (buffer addr : 0x302CD8)
-I- 	0xD28 bytes written by applet
-I---------------------------------
-I-        Script Completed       -
-I-     Please Reset the Device   -
-I---------------------------------


#2

You ate repeating the same mistake. You are now done loading tinybooter and it is time to load the firmware. Please spend couple minutes and read the firmware update page on wiki. This will save you and us a lot of time :slight_smile:


#3

!#$!#$!@ #$!#$

So, sorry. I’ll remember that step about time the firmware updater starts working normally… :frowning:


#4

So is it working?


#5

Yes, like a charm so far! Like it should when ALL the steps are followed… Thanks.


#6

I was so worried. Glad it is working for you.