I have the Raptor connected to a N8 display (no other connections). Upon power up: for a short period, I have a white screen and the USB ding dong, but then the DPclient LED is blinking and the screen flashes in sync. I disconnected the display and followed the “G400 Bootloader Installation”. Please see the screen shot attached. Any chance of a recovery?
Thanks,
Kevin.
Hmm, Device Manager shows the device in bootloader mode correctly…
The times I’ve seen that actual error prompt, I found I had something else open and connected to the COM port so the script couldn’t attach to it; it is possible that there’s something else, but that was what I saw (as recent as Friday :
)
If I remember correctly, you need to run the Batch command with Administrative privileges.
@ scardinate Yes I had forgotten to select “Run as administrator” For a moment I thought that’s it! But have the same error message… Many thanks.
@ Brett Yes I had FEZ Config open. I ran Flash Bootloader.bat again as Administrator and :
The install process will take a few minutes. Once the install has completed successfully,
“Bootloader Install Complete” will be displayed. The "G400/FEZ Hydra Loader Updater"
must be installed for this script to function.
Please enter the number part of the COM port of the G400.
For example: enter only the number 10 for COM10.
COM Port Number: 3
Updating…
-I- Waiting …
-I- TCL platform : Windows NT
-I- SAM-BA 2.12 on : windows
current connection is \USBserial\COM3, \USBserial\COM3 to be matched
-I- Retrieved arguments from command line :
-I- argv 0 : \USBserial\COM3
-I- argv 1 : at91sam9g15-ek
-I- argv 2 : Bootloader.tcl
-I- Connection : \USBserial\COM3 (target(comType) = 0)
-I- Board : at91sam9g15-ek
-I- Traces Level : 4
-I- target(handle) : 52119520
Read device Chip ID at 0xfffff240 — get 0x819a05a1
-I- Found processor : at91sam9g15 (Chip ID : 0x819a05a1)
sourcing device file C:/Program Files (x86)/Atmel/sam-ba_2.12/sam-ba.exe/…/tcl_lib/devices/at91sam9g15.tcl
sourcing board description file C:/Program Files (x86)/Atmel/sam-ba_2.12/sam-ba.exe/…/tcl_lib/at91sam9g15-ek/at91sam9g15-ek.tcl
-I- Loading applet applet-lowlevelinit-sam9g15.bin at address 0x300000
-I- Memory Size : 0x0 bytes
-I- Buffer address : 0x4
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- Low level initialized
-I- External RAM Settings : extRamVdd=0, extRamType=1, extRamDataBusWidth=32, extDDRamModel=0
-I- External RAM Settings : extRamVdd=0, extRamType=1, extRamDataBusWidth=32, extDDRamModel=0
-I- Loading applet applet-extram-sam9g15.bin at address 0x300000
-I- Memory Size : 0x8000000 bytes
-I- Buffer address : 0x300B90
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- External RAM initialized
-I- Command line mode : Execute script file : Bootloader.tcl
-E- Script File Bootloader.tcl returned error : couldn’t read file “Bootloader.tcl”: no such file or directory - couldn’t read file “Bootloader.tcl”: no such file or directory
while executing
"source $scriptFile"
You can find the above log at C:\Users\kevin\AppData\Local\Temp\GHI Electronics G400 Bootloader Update Log-3292-44.04.txt.
Press any key to continue . . .
Bootloader.tcl is in the same directory:
G400 Bootloader Flasher
Copyright © GHI Electronics 2015
All rights reserved.
GENERIC::Init $RAM::appletAddr $RAM::appletMailboxAddr $RAM::appletFileName [list $::target(comType) $::target(traceLevel) $BOARD::extRamVdd $BOARD::extRamType $BOARD::extRamDataBusWidth $BOARD::extDDRamModel]
DATAFLASH::Init 0
DATAFLASH::EraseAll
GENERIC::SendFile “Bootloader.bin” 0x0 1
puts ""
puts “Bootloader Update Complete”
Tried a second time. Error a little different:
The install process will take a few minutes. Once the install has completed successfully,
“Bootloader Install Complete” will be displayed. The "G400/FEZ Hydra Loader Updater"
must be installed for this script to function.
Please enter the number part of the COM port of the G400.
For example: enter only the number 10 for COM10.
COM Port Number: 3
Updating…
-I- Waiting …
-I- TCL platform : Windows NT
-I- SAM-BA 2.12 on : windows
current connection is \USBserial\COM3, \USBserial\COM3 to be matched
-I- Retrieved arguments from command line :
-I- argv 0 : \USBserial\COM3
-I- argv 1 : at91sam9g15-ek
-I- argv 2 : Bootloader.tcl
-I- Connection : \USBserial\COM3 (target(comType) = 0)
-I- Board : at91sam9g15-ek
-I- Traces Level : 4
-I- target(handle) : 52046064
Read device Chip ID at 0xfffff240 — get 0x819a05a1
-I- Found processor : at91sam9g15 (Chip ID : 0x819a05a1)
sourcing device file C:/Program Files (x86)/Atmel/sam-ba_2.12/sam-ba.exe/…/tcl_lib/devices/at91sam9g15.tcl
sourcing board description file C:/Program Files (x86)/Atmel/sam-ba_2.12/sam-ba.exe/…/tcl_lib/at91sam9g15-ek/at91sam9g15-ek.tcl
-I- Loading applet applet-lowlevelinit-sam9g15.bin at address 0x300000
-I- Memory Size : 0x0 bytes
-I- Buffer address : 0x4
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- Low level initialized
-I- External RAM Settings : extRamVdd=0, extRamType=1, extRamDataBusWidth=32, extDDRamModel=0
-I- External RAM Settings : extRamVdd=0, extRamType=1, extRamDataBusWidth=32, extDDRamModel=0
-I- Loading applet applet-extram-sam9g15.bin at address 0x300000
-E- Error during external RAM initialization.
-E- External RAM access is required to run applets.
-E- Connection abort
You can find the above log at C:\Users\kevin\AppData\Local\Temp\GHI Electronics G400 Bootloader Update Log-5409-32.93.txt.
Press any key to continue . . .
Not looking good?
@ KG1 - The latest scripts do not, and cannot, be run as an Administrator. Just double click the script and enter the COM port. The error you are seeing usually occurs, as has been suggested, when the COM port is opened or not closed properly, a reboot should fix that. To your original problem, it sounds like the USB Client DP is bad or not getting enough power. Try the firmware update with the display removed from your system, another USB Client DP if available, a different USB port, and a different PC if it still fails.
@ John I replaced the USB Client DP board. Both red led are steady and the screen is white (no longer flashing). I rebooted the PC and connected the USB cable to my PC. The Bossa Program port appears in the Device Manager without applying pin 8 on socket 3 to ground. Running Flash Bootloader.bat still outputs error:
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- DATAFLASH::Init 0 (trace level : 4)
-I- Loading applet applet-dataflash-sam9g15.bin at address 0x20000000
-E- Script File Bootloader.tcl returned error : Error Initializing DataFlash Applet (Can’t detect known device) - Error Initializing DataFlash Applet (Can’t detect known device)
while executing
"error “Error Initializing DataFlash Applet ($dummy_err)”"
(procedure “DATAFLASH::Init” line 14)
invoked from within
"DATAFLASH::Init 0"
(file “Bootloader.tcl” line 7)
invoked from within
"source $scriptFile"
Please comment…
Kevin
@ KG1 - Did the Raptor work at one point? Is there a second computer you can try this process on?
@ John I have tried a less reliable pc. The test above was on a Windows 10 machine which I have used successfully in the past. The Raptor was installed in a robot at the time it failed (screen began flashing). Just guessing but I think back emf from the motor in a actuator may have sent a pulse to the USB Client DP.
Since the purchase of a new USB Client DP the led on the raptor is not flashing but the screen is white.
@ KG1 - Unfortunately it seems likely that whatever killed the USB Client DP module also killed the Raptor if Flash Bootloader.bat continues to error with “Can’t detect known device” on multiple computers.
@ John, Your help is appreciated. I used Zener Diodes on the 5V line but not on the 12V line. Can’t see any chip damage under magnification. However with bigger motors the problems grow. Processors should have separate batteries I guess!
Thanks,
Kevin.