@ bghavami - Did the board ever work for you?
It never worked.
Can you ship me a replacement?
@ bghavami - Go ahead and contact support at ghielectronics.com for an RMA. Reference this thread.
I just submitted a message to Support from Company --> Contact Us.
Thanks for all your help.
@ bghavami - Weāre happy to help.
Hi John,
I got the new board in today. It is doing the same! I followed the instructions as outlines in ā.NET Micro Framework ā GHI Electronicsā. Is there any documentation that shows what USB port use, what buttons to push, and what jumper to set to get started on G120E development board? This is getting very frustrating for me. I appreciate any help.
Iām not sure what you mean by āWhat USB port to useā. I donāt have the G120E dev board but I have a Spider 2 which uses the same G120E module. Looking at the picture of yoru dev board I see one connector on top right labeled āUSB Debugā which is how you would connect it to your PC for programming/debugging and updating the firmware. The āUSB Hostā connector is for USB devices (like a thumbdrive) that you might plug into the dev board. If you want to update the Tiny Booter there are two pins on the G120E that need to be pulled down (P2.10 and P0.22 as I recall) on my Spider there are dip switches for that, on the G120E Dev board it looks like those line are used for two of the buttons, so you would hold those two buttons down and press reset to get into Tiny Booter update mode.
The G210E Dev Board uses the G210E module, download the schematic for the dev board and the datasheet for the module.
you must use the āUSB Debugā port. That is the only one that has the appropriate connections that will allow the full device to be seen by the PC
You should consider if the USB port on your computer can supply sufficient current to run this board on itās own (and use a quality cable to ensure you can deliver that current to the board). Powering the device via the power input plug at the same time as you connect the USB to the USB Debug port is supported and suggested where you use the screen.
On startup, there are no buttons that you need to press. The startup is documented in the G120 and G120E datasheet/manual (page 10). You can hold the device in reset by holding down the reset button - when you release it, and assuming you have an appropriate connection for power and to the PC, the device should become visible to Windows and you should hear/see the device connection noise and action in Device Manager.
To boot into the tinybooter or the GHI bootloader, you can see the state table on page 10. Doing nothing should allow the device to boot into application mode. LDR0 and LDR1 pins are documented on Page 8 for the G120E. LDR0 = P2.10, LDR1 = P0.22. From the schematics, LDR0 = the UP button, and LDR1 = DOWN button. So with the device in reset, press and hold LDR0 and/or LDR1 to get into the loader modes you need.
But the fundamentals - if you connect a working cable to the USB Debug micro-USB connector and your computer, you should have the board recognised by Windows and you should then be able to see the device.
Thanks to both of you Jeff and Brett,
I didnāt want to answer to both of you until have cleared every possible way that I could fix the problem.
Brett, my hardware connection is as you described, The board is powered by a good quality 12 volt/ 5 amp power supply and I am using the provided USB cable that was shipped with G120E board. After countless hours of research and trying different things, I have narrowed down my question to why the installed USB device G120 (as seen in Device Manger in the first image) is not recognized by either FEZ-Config or MFDeploy (see the next 2 images)? Is there any problems with the USB device driver compatibility or access security! See the image of G120 USB device properties in the last image.
Thanks.
@ bghavami - The first thing that comes to mind is there is a problem with your SDK. Your last images shows the driver as not being digitally signed. Our drivers our signed, so something has messed up your install.
How do I correct this?
@ bghavami - Redownload and reinstall the SDK, try another computer, make sure that C:\Program Files (x86)\GHI Electronics\USB Drivers\NETMF Interface\GHI_NETMF_Interface.cat has a valid digital signature by checking the Digital Signatures tab under Properties. Also open the file and make sure Windows says the security catalog is valid.
There are only two files on entire drive C: where G120E is installed that are related to GHI-NETFM_Interface:
GHI_NETMF_Interface.cat
GHI_NETMF_Interface.inf
The security signatures are displayed in the attached images.
Do you see anything wrong with these two signature?
@ bghavami - Where are those files located?
They are located in the following folder:
C:\Program Files (x86)\GHI Electronics\USB Drivers\NETMF Interface
Removed existing G120 USB driver from Device Manger, then installed the certificate from the GHI_NETMF_Interface.cat (see install images). An unknown usb device appeared in Devcei Manger. I updated the device driver and pointed it to C:\Program Files (x86)\GHI Electronics\USB Drivers\NETMF Interface folder. Now the device driver has a signature! But still I am not able too see it in either MFDeploy or GHI Config.
Sorry, here are the images.
I did one more test, loaded the āC:\Program Files (x86)\GHI Electronics\NETMF v4.3 SDK\Firmwares\G120\Loader.ghiā manually (see the image), after the successful XMODEM transfer, I issued the āRā command the response was āBad Firmwareā. What does this one mean?? :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall: :wall:
John suggested you re-download the SDK and uninstall your previous one and reinstall. Iām not sure if you did that or not?
The ābad firmwareā is often just that, a bad download or a bad transfer. I suggest if you didnāt reinstall the SDK that you do so again. You can safely try sending the firmware multiple times. Please also make sure you use the correct transfer options with XMODEM as itās critical to the process. Try erasing and uploading again multiple times, resetting the device in between, to see if any of those things help.
Do you have access to another PC (say a Win 8.1 device) that hasnāt had the SDK installed before? Might be worth a try to get a parallel setup working.
I just dusted off a brand new Cobra 3 that had never been opened. OK, I opened itās ziplock bag for the first time - anyway it was brand new and had never been setup. Iām on a Surface Book running Win10 Insider build (14291). Iāve got SDK 2016 R1 beta installed
I put it in bootloader mode (held LDR0 + LDR1 and reset it) and then ran Fez Config. Then I made it do a firmware update, and it all worked.
I installed Teraterm, and again put the device in bootloader mode.
[quote]Force Boot Loader detected
GHI loader commands are now active
BL
BL
BL (me type V)
1.01
BL (me type E)
Erase all memory! Are you sure? (me type Y)
Erasingā¦
Done.
BL (me type V)
1.01
BL (me type X)
Start File Transfer
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
(me select XMODEM send with 1k option and select loader.ghi file)
File Transfer Finished Successfully
BL (me type V)
1.01
BL
[/quote]
I deleted all downloaded installation files from my system. Uninstalled both .NET Micro Framework SDK 4.3 (SDK-QDE2) and GHI NETFM SDK 2016 R1. Downloaded both .NET Micro Framework SDK 4.3 (SDK-QDE2) and GHI NETFM SDK 2015 R1 (GHI NETFM SDK 2016 R1 was missing from the WEB site for now).
I put G120E in bootloader mode (held LDR0 + LDR1 and reset it) and then ran Fez Config. and did a firmware update, it did not work.
Then I followed your instruction using Tera Term V 4.5.3, I put the device in bootloader mode. At the XMODEM file transfer selected Loader.ghi. I noticed the file length is zero! I backed out and restarted Tera Term in Administrative mode. This time the file length was 49k
Also, I noticed when I use V command it tells me the version number is 1.02 not 1.01. I am not sure if this makes any difference?
BL
1.02
E
Erase all memory! Are you sure? Y
Erasingā¦
Done.
V
1.02
BL
X
Start File Transfer
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
(me select XMODEM send with 1k option and select loader.ghi file)
File Transfer Finished Successfully
At this point the screen freezes, because the script automatically sends an āRā command to G120E enabling the USB and disabling the serial port.
The good news is that I am not getting the Bad Firmware error any more. The bad news is neither GHI Config nor MFDeploy see the USB port G120. I do, however, see the G120 USB in the āUniversal Serial Bus devicesā with in Device Manager! Why is G120 USB not in āUniversal Serial Bus controllerā class section of Device manager?
At this point I am loading a brand new workstation with Windows 10 and nothing else. Iāll post the results tomorrow. I am pretty sure security setting on my current workstation is preventing FEZ Config and MFDeploy from seeing the G120 USB Port.
Thanks.