I wasted 5 hours on looking for an answer, i was looking for 6 months ago, and now i have not learned anything from that.
I wanted to do a Upgrade on NETMF and thought i have to flash it from scratch. I updated the G400 with the SAM BA software, and then it is shown as GHI Bootloader Interface.
After that i wanted to upload TinyBooter but somehow the G400 Bootloader ghi file, which i had back then is missing and i’m not able to even selcect the “G400” in Loader Update.
G400 Bootloader Installation text…
This process may only be completed for the 2016 R1 SDK and later. Earlier SDKs do not contain a loader compatible with the bootloader.
watch device manager at the same time. If you’re in the right mode you’ll see a serial port; if you’re not in the right mode, you won’t.
And just a tip. When you have a prolonged debugging session like this, a best practice to get the best help quickest is to give a full summary of what the status is. So in your case it’d be worth documenting what you did as you were stepping through the upgrade process in Fez Config and where the error arrived.
@ Brett - Ok so first i updated the G400 via the Batch-Script referring to the SAM-BA Tool.
Then i restarted the device (unplugged power & plugged power back in) and it has been listed as a GHI Bootloader interface.
After that i’ve started fez config and tried to upload the 2 hex files via the “upload bootloader” option from the “advanced” tab.
When i’ve selected the G400, the using com port and the GHI. file, Fez config selected the 2 hex files itsself.
When i pressed upload, Fez config throws the error message as i already mentioned.
@ quickshat
You wrote: ’ I updated the G400 with the SAM BA software’
I use G400 (Raptor and G400Dev). As well as I remember, the SAM BA was the old way to upgrade the G400, hence I presume you did not tookre of the link I pointed you. Of course, I may be wrong, but I fully agree with @ Brett.
Too often, people made a request for help, but don’t provide the usefull information, i.e. a step by step of what was done, the exact messages they receive, etc. Some tell even just “It doesn’t work” !.
We upgraded our Raptor stricktly following the instructions, and even reported an error in the instructions (a wrong pin#) and it was since fixed.
We use VS 2015, even in debug mode, and an application is running 24/24 7/7 on the Raptor, and has acquired about 100 M of measures from various sensors, the system clock is updated using NTP with WiFi, the data is stored on a 32 GB SD card, graphics displayed on T43. All without any issue.
MODE bin does select the the USB/Serial mode. IF there are more than 1 serial port on the device i should use COM1 → MODE Pins state ??
I mean how should it help me using mode pin, when i’m told to use the COM1 which is nothing else than a FTDI → Com port in Device Manager
You have only the choice between the USB interface on the GHI board and the serial COM1 *on the GHI board° (there may be more Serial ports on the board), but only COM1 is suitable for that purpose.
These are two different connectors.
The selection between USB and Serial is determined by the state of the MODE pin at reset time.
On the PC side, while using USB, your board may appear as COM4 or COM7 or any other COM#… It has nothing to do with the COM1 on the board.
I know that the numeration in the DevMng has nothing to do with it…
I have connected the usb cable to COM1 and it is recognized as a simple COm port in DevMng.
Fez Config denys the upload to a Serial Port.
Why?
If i am connecting it with the Usb-OTG interface (Debug) it is shown as Com prot named: GHI Bootloader interface…
Both are not working with Fez Config
@ quickshat - Try to upload the firmware again, it may have been a random serial corruption. If it still fails, can you try to redownload and reinstall the SDK and then try again?