We have been using G80s on our products for years now and this newest shipment isn’t working like the previous. Normally we open FEZconfig, the GHI bootloader COM appears, we update Tinybooter, then load our HEX file.
This time it seems different. GHI Bootloader isn’t coming up. I’m getting ‘STM device in DFU Mode’. Has something changed. Is there an alternative to FEZconfig? Why am I getting something in DfuSE Demo? If I have to load something why isn’t there a G80 bootloader .dfu available.
Thanks Gus. It sure does seem that they are ST chips although they were ordered from Mouser/Digikey. If they were ST chips would the markings on the chip be different? If they do end up being ST chips is there anything we can do?
We also have the same issue for G80 purchased from Mouser on August 2019 , kindly update us as we have finished the PCBA. we are using NETMF on G80, expecting your reply at the earliest
you need to reach out to GHI directly via their website, rather than just here, because this is not a formal channel into the company. You should also raise it with Mouser.
we have already sent email to support@ghielectronics.com along with tech@mouser.com for further assistance, but we did not receive any formal reply or acknowledgment to this time, waiting to solve the issue as the PCBA is completed.
This a tested and proven board and we had produced 100 + pcs in the last two months and deployed and was perfect. This issue is only with this batch of G80 SOCwhich was purchased from Mouser
I think we have a batch of G80s that we ordered ~a year ago that exhibit this behavior. Occasionally someone puts one on a PCB and they want me to program it. Is there any workaround? Or do we just have to replace the microcontroller? Thanks!
