Can't connect anymore with my SC20260D Rev A

SITCore Modules & Chipsets
1

Hi

Being now retired I have now more to time to ‘play’ with my GHI Boards.
Everything was working fine so far.
Unfortunately since this morning, I am not able anymore to connect to the SC20260D board
Got this message while trying to deploy the app: one error has occurred, please check your hardware

I have no problem with the SC20100 or any other GHI board (Feather, FEZ Portal, Flea, Fez …
I use a power USB hub + dedicated PS for the SC200260. Already tried with another cable
Nothing plugged on the board, no display

I opened TinyCLR Config got USB 3 and 4 listed.
I tried to connect with both, but TinyCLR got frozen

I removed the display, reseat the module and retried but no luck
I always got the message USB Not recognized

Rebooted several times and finally got
COM3 - COM4 and COM7 (GHI Electronics)
I selected COM7, got it connected but showing a firmware 2.1 (while 2.3.0.2000) is installed

Updated the firmware successfully to 2.3.0.2000 but could not reconnect the board after disconnecting.
Showing again only COM3 - COM4

The Device Manager shows the device as unknown

Screenshot 2025-02-10 122628
Screenshot 2025-02-10 122628582×415 84.2 KB

Should I consider the board or DIMM module as defective ?
Any hints ?

Thanks

2

I would not assume it is dead yet.

Go into loader mode and erase all. And restart your PC.

3

Well, as had issue with the SC20260, I switch to the SC20100 and did further testing with the Wifi 7 click.
Then I stopped for one hour and when i came back, I was not able to deploy the app to the SC20100 anymore.

None of the boards appear in the TinyCLR Config selection

Tried with different cables, usb port, reboot…
No changes

If I connect the FEZ portal, it’s all good but as I don’t want to have the same issue in a few hours, I am really hesitant to change the board again

Sound really weird

Tried both on my laptop (win 11) and on my old surface (win 10)
Same. The SC20260 and SC20100 do not appear anymore

4

Ok. I used the wrong button (boot) to set the board in bootloader mode