FEZ Hydra - Unable to update TinyBootoer Updater using CommandPrompt

[Win]

I just get Hydra today; I’m new to Gadgeteer. I use Hydra Update to update the firmware.

Gone through 1 - 5 steps
Step 6 - Press RESET, but I’m not sure what screen to look at.

My computer detect the hydra as “GPS Camera Detect (COM3)”. So I go head and update C:\Program Files\GHI Electronics\GHI Electronics OSH NETMF v4.1 SDK\FEZ Hydra\Firmware\FEZ Hydra TinyBooter Updater\CommandPrompt com3

I get the following error. Now Hydra Update cannot Ping.

Appreciate your help!

Note: Step 3 - I have tried with both SD card and wire. Both methods are not working.

-I- Waiting …
-I- TCL platform : Windows NT
-I- SAM-BA CDC 2.10 on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : com3
-I- argv 1 : at91sam9rl64-ek
-I- argv 2 : TinyBooterLoader.tcl
-I- Connection : com3 (target(comType) = 3)
-I- Board : at91sam9rl64-ek
-I- Traces Level : 4
-I- target(handle) : file13f7600
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 0x3180
-I- Erasing: 0x18C0 bytes at address 0x4A40
-I- Erasing: 0x18C0 bytes at address 0x6300
-I- Erasing: 0x18C0 bytes at address 0x7BC0
-I- Erasing: 0x18C0 bytes at address 0x9480
-I- Erasing: 0x18C0 bytes at address 0xAD40
-I- Erasing: 0x18C0 bytes at address 0xC600
-I- Erasing: 0x18C0 bytes at address 0xDEC0
-I- Erasing: 0x18C0 bytes at address 0xF780
-I- Erasing: 0x18C0 bytes at address 0x11040
-I- Erasing: 0x18C0 bytes at address 0x12900
-I- Erasing: 0x18C0 bytes at address 0x141C0
-I- Erasing: 0x18C0 bytes at address 0x15A80
-I- Erasing: 0x18C0 bytes at address 0x17340
-I- Erasing: 0x18C0 bytes at address 0x18C00
-I- Erasing: 0x18C0 bytes at address 0x1A4C0
-I- Erasing: 0x18C0 bytes at address 0x1BD80
-I- Erasing: 0x18C0 bytes at address 0x1D640
-I- Erasing: 0x18C0 bytes at address 0x1EF00
-I- Erasing: 0x18C0 bytes at address 0x207C0
-I- Erasing: 0x18C0 bytes at address 0x22080
-I- Erasing: 0x18C0 bytes at address 0x23940
-I- Erasing: 0x18C0 bytes at address 0x25200
-I- Erasing: 0x18C0 bytes at address 0x26AC0
-I- Erasing: 0x18C0 bytes at address 0x28380
-I- Erasing: 0x18C0 bytes at address 0x29C40
-I- Erasing: 0x18C0 bytes at address 0x2B500
-I- Erasing: 0x18C0 bytes at address 0x2CDC0
-I- Erasing: 0x18C0 bytes at address 0x2E680
-I- Erasing: 0x18C0 bytes at address 0x2FF40
-I- Erasing: 0x18C0 bytes at address 0x31800
-I- Erasing: 0x18C0 bytes at address 0x330C0
-I- Erasing: 0x18C0 bytes at address 0x34980
-I- Erasing: 0x18C0 bytes at address 0x36240
-I- Erasing: 0x18C0 bytes at address 0x37B00
-I- Erasing: 0x18C0 bytes at address 0x393C0
-I- Erasing: 0x18C0 bytes at address 0x3AC80
-I- Erasing: 0x18C0 bytes at address 0x3C540
-I- Erasing: 0x18C0 bytes at address 0x3DE00
-I- Erasing: 0x18C0 bytes at address 0x3F6C0
-I- Erasing: 0x18C0 bytes at address 0x40F80
-I- Erasing: 0x18C0 bytes at address 0x42840
-I- Erasing: 0x18C0 bytes at address 0x44100
-I- Erasing: 0x18C0 bytes at address 0x459C0
-I- Erasing: 0x18C0 bytes at address 0x47280
-I- Erasing: 0x18C0 bytes at address 0x48B40
-I- Erasing: 0x18C0 bytes at address 0x4A400
-I- Erasing: 0x18C0 bytes at address 0x4BCC0
-I- Erasing: 0x18C0 bytes at address 0x4D580
-I- Erasing: 0x18C0 bytes at address 0x4EE40
-I- Erasing: 0x18C0 bytes at address 0x50700
-I- Erasing: 0x18C0 bytes at address 0x51FC0
-I- Erasing: 0x18C0 bytes at address 0x53880
-I- Erasing: 0x18C0 bytes at address 0x55140
-I- Erasing: 0x18C0 bytes at address 0x56A00
-I- Erasing: 0x18C0 bytes at address 0x582C0
-I- Erasing: 0x18C0 bytes at address 0x59B80
-I- Erasing: 0x18C0 bytes at address 0x5B440
-I- Erasing: 0x18C0 bytes at address 0x5CD00
-I- Erasing: 0x18C0 bytes at address 0x5E5C0
-I- Erasing: 0x18C0 bytes at address 0x5FE80
-I- Erasing: 0x18C0 bytes at address 0x61740
-I- Erasing: 0x18C0 bytes at address 0x63000
-I- Erasing: 0x18C0 bytes at address 0x648C0
-I- Erasing: 0x18C0 bytes at address 0x66180
-I- Erasing: 0x18C0 bytes at address 0x67A40
-I- Erasing: 0x18C0 bytes at address 0x69300
-I- Erasing: 0x18C0 bytes at address 0x6ABC0
-I- Erasing: 0x18C0 bytes at address 0x6C480
-I- Erasing: 0x18C0 bytes at address 0x6DD40
-I- Erasing: 0x18C0 bytes at address 0x6F600
-I- Erasing: 0x18C0 bytes at address 0x70EC0
-I- Erasing: 0x18C0 bytes at address 0x72780
-I- Erasing: 0x18C0 bytes at address 0x74040
-I- Erasing: 0x18C0 bytes at address 0x75900
-I- Erasing: 0x18C0 bytes at address 0x771C0
-I- Erasing: 0x18C0 bytes at address 0x78A80
-I- Erasing: 0x18C0 bytes at address 0x7A340
-I- Erasing: 0x18C0 bytes at address 0x7BC00
-I- Erasing: 0x18C0 bytes at address 0x7D4C0
-I- Erasing: 0x18C0 bytes at address 0x7ED80
-I- Erasing: 0x18C0 bytes at address 0x80640
-I- Erasing: 0x18C0 bytes at address 0x81F00
-I- Erasing: 0x18C0 bytes at address 0x837C0
-I- Erasing: 0x18C0 bytes at address 0x85080
-I- Erasing: 0x18C0 bytes at address 0x86940
-I- Erasing: 0x18C0 bytes at address 0x88200
-I- Erasing: 0x18C0 bytes at address 0x89AC0
-I- Erasing: 0x18C0 bytes at address 0x8B380
-I- Erasing: 0x18C0 bytes at address 0x8CC40
-I- Erasing: 0x18C0 bytes at address 0x8E500
-I- Erasing: 0x18C0 bytes at address 0x8FDC0
-I- Erasing: 0x18C0 bytes at address 0x91680
-I- Erasing: 0x18C0 bytes at address 0x92F40
-I- Erasing: 0x18C0 bytes at address 0x94800
-I- Erasing: 0x18C0 bytes at address 0x960C0
-I- Erasing: 0x18C0 bytes at address 0x97980
-I- Erasing: 0x18C0 bytes at address 0x99240
-I- Erasing: 0x18C0 bytes at address 0x9AB00
-I- Erasing: 0x18C0 bytes at address 0x9C3C0
-I- Erasing: 0x18C0 bytes at address 0x9DC80
-I- Erasing: 0x18C0 bytes at address 0x9F540
-I- Erasing: 0x18C0 bytes at address 0xA0E00
-I- Erasing: 0x18C0 bytes at address 0xA26C0
-I- Erasing: 0x18C0 bytes at address 0xA3F80
-I- Erasing: 0x18C0 bytes at address 0xA5840
-I- Erasing: 0x18C0 bytes at address 0xA7100
-I- Erasing: 0x18C0 bytes at address 0xA89C0
-I- Erasing: 0x18C0 bytes at address 0xAA280

[Brett]

Hi Wim,

welcome to the forums !

I just dug out my Hydra, because I have only done this once (when I got the device!)

So first up, are you using SD card? Wire? JP1?

You first asked about “what screen”. If you have a screen attached to the Fez, that’s the one. If you don’t have a screen attached, that’s ok, just ignore this

When I go through the update process, here’s what I did.

I first made sure I had the SD card boot.bin file ready. To do that I used the FEZHydraMainboardUpdater.exe app, inserted my SD card in my PC’s SD reader, then used the updater to write it to the SD card. Then I removed the SD card, and with the Hydra disconnected from the PC I connected SD module to F and powered it up; 30 seconds later I pulled the power out and removed the SD card module.

On reconnecting the device, I got the GPS Camera Detect device listed in Device Manager, on COM6.

I then selected the Image files, making sure you select either the normal or ethernet firmware you want; make sure you select both the ER_CONFIG and ER_FLASH portions.

I then clicked UPDATE; it goes through the update process S…L…O…W…L…Y… because there’s a lot of memory to write First it is erasing the memory. Come back a bit later, and I’ll tell you what’s next

[Brett]

so it takes a good few minutes alone to erase the memory; then the tinybooter gets loaded pretty quick but you do need to reset the device and click NEXT.

iI looks to me like your erase stopped part way through. You need to go back to loading the boot.bin again, and then move forward with the loading of everything again. Good luck !

[Dat_Tran]

The newest Hydra Updater 1.0.3 application, you even don’t need SD card, wire… to erase flash. Only thing you need to do is click ‘Update button’ and follow its step.

[ianlee74]

[Brett]

Ah good point, I’m still on the previous build. Downloading

[Win]

I use [italic]Hydra Updater 1.0.3 application [/italic] as Dat suggested, and it works like a charm. I don’t even need to erase flash.

I’m a happy camper now. TinyCLR community support is overwhelmingly excellent.

@ Brett, janlee74 and Dat - Thank you all for your help!

[Brett]

fantastic news. Now get Fezzing !!! ;D

[Gus_Issa]

My guess you will spend the weekend having fun with hardware.

Enjoy and welcome to the community.

[srivatsan]

where do i download “Hydra Updater 1.0.3 application”?

[Gus_Issa]

@srivatsan

where do i download “Hydra Updater 1.0.3 application”?

Everything you need is in one download “the package” Support - GHI Electronics

[srivatsan]

I installed the new version. Now i am getting the following error.
– Log –
Connecting to device… Fail.
Please wait for trying to reconnect…
Cannot connect to the device! Follow steps 1 to 4

Previously when i tried with the old version, the erasing step hung and i terminated the entire process. From then on there is no response from the device.

[Gus_Issa]

If updater failed then try the wiki for manual update.

[srivatsan]

I am trying the manual step where it asks me to go the following folder
C:\Program Files (x86)\GHI Electronics\GHI Electronics OSH NETMF v4.1 SDK\

Under this folder i only have one release notes folder. I dont have a folder called Fez Hydra. Not sure where i messed something

[Gus_Issa]

How did you get there?!

Here is the link GHI Electronics – Where Hardware Meets Software

[srivatsan]

i was also looking at the same URL. But i found my issue. I was not looking at the right directories in my machine. just found the files…updating now

[srivatsan]

Everything went great and i am back in business… thanks