I understand that you try to update only the Image (nk_ce7.nb0).
did you start with 2.3? (like the the screenshot)
what version of the Image did you download? (2.3?)
could it be that the nk_ce7.nb0 file is corrupt? (maybe the SD Card is not ok?)
You say after the update there is no output on the screen, but since you did not touch the Bootloader that one should still be OK and produce some initial display output.
Also can you try to check the serial debug output? maybe there is something there.
To restore the module, just use the USB recovery procedure:
I heard from another customer that there might be an issue with some SD Cards. I’m investigating that. Can you try to do the update from a USB Stick instead?
The workaround you provided for SD Card works perfectly! Thank you.
I have another question that I encountered before the OS image of the module was broken. The connection between my development PC and the module through USB cable is not working.
I have seen this article and disabled ActiveSync Connection. But it remains the same.
Is there any other settings I should do before connecting them? My PC didn’t show any message or install driver when I connected them by a USB to USB cable. I tried micro USB to USB cable too. Both are not workable. Do you have any ideas about it?
I guess you’re using Windows 10 on your PC… so it’s a bit complicated to make it work there as MS did not care about compatibility anymore…
First of all ActiveSync was replace by Mobile Device Center on the PC side…
But because of some Windows 10 updates the functionality was completely broken some years ago…
Actually, I have another wince device that works. (Not Toradex module) The Windows Mobile Device Center was activated once I connected the device with USB cable.
But the module - T20 that I used did not response. I’ve tried to fix the USB communication by following the article, but still not working. Do I need to set the registry or something to solve this issue?
Another issue, I’ve tried to enter recovery mode by hardware mechanism. But I was still not able to see the module as APX device. So if I’d like to reset the whole module, is there any article that can be reference?
It’s very strange that even recovery mode does not work.
Maybe there is a USB issue on the carrier board you’re using. Which one you use? Colibri Evaluation board?
Maybe the USB_DET Jumper is missing or not contacting properly?
I’ve recovered my core board - T20 by using Colibri Evaluation Board to enter recovery mode, put it back to my customized carrier board. Everything’s fine.
Then I also built and updated OS image with drivers that I need. But OS shows normal with Colibri Evaluation Board, not with my customized carrier board.
OS image V2.3 <— Both carrier boards are OK.
Custom Built OS image ← Colibri Evaluation Board OK, the other one FAIL.
I think there’s some differences of build options. Could you tell me how to set those options?
[upload|0LMSUEujg7o3bJrwKcib7rXJIVE=]
[upload|bNbuK5AXpvhi9KPKA1BNwjAA9fk=]
[upload|v5Ayd9hb1q22MgCwOxLnA6XQ43Y=]
I’m not sure what you changed from out default Workspace. The best thing would be to compare our original pbxml workspace file with your modified one. The settings you show are only a very little part of what you can customize.
Also to narrow down the problem it would be helpful if you elaborate on what is failing with your custom build image on your HW. can you send me the serial debug output? So i can see where the boot process stops.