search

Samraksh / eMote

eMote OS -- Multiple Ports (using .NET MF v4.3)
0 stars 0 forks source link

Cannot "reboot and stop" when "waiting for debug commands" #459

Closed Nathan-Stohs closed 7 years ago

Nathan-Stohs commented 7 years ago

If a bad TinyCLR is loaded, this problem can half-brick the device and require TB pins (which don't exist on WLN) or JTAG intervention.

example below:

Assembly: Samraksh_eMote (4.3.2.7)***********************************************************************
*                                                                     *
* ERROR!!!!  Firmware version does not match managed code version!!!! *
*                                                                     *
*                                                                     *
* Invalid native checksum: Samraksh_eMote 0xFAEF3F35!=0xCD4EF9B0 *
*                                                                     *
***********************************************************************
 Resolving.
Link failure: some assembly references cannot be resolved!!

Assembly: Samraksh.VirtualFence.Component.AppMsgHandler (1.0.6115.17645) needs assembly 'Utility' (1.24.1.0)
Assembly: Samraksh.VirtualFence.Component.AppMsgHandler (1.0.6115.17645) needs assembly 'Samraksh.VirtualFence.Component.Routing' (1.0.0.0)
Assembly: Samraksh.VirtualFence.Component.AppMsgHandler (1.0.6115.17645) needs assembly 'Samraksh.VirtualFence.Component.AppGlobal' (1.0.6115.17643)
Assembly: Samraksh.VirtualFence.Component.AppGlobal (1.0.6115.17643) needs assembly 'Utility' (1.24.1.0)
Assembly: Samraksh.Manager.Component.NetManager (1.0.0.0) needs assembly 'Samraksh.VirtualFence.Component.Routing' (1.0.0.0)
Assembly: Samraksh.Manager.Component.NetManager (1.0.0.0) needs assembly 'Utility' (1.24.1.0)
Assembly: Samraksh.Manager.Component.NetManager (1.0.0.0) needs assembly 'Samraksh.Manager.Component.NetManagerGlobal' (1.0.0.0)
Error: a3000000
Reboot and Stop Command
Error: No response from device
Reboot and Stop Complete
Waiting for debug commands...

In the above case there is no opportunity to enter TinyBooter. Perhaps we need to make a hardware route here.

ChrisAtSamraksh commented 7 years ago

Reboot and Stop doesn't work?

Nathan-Stohs commented 7 years ago

Normally it does work, but it seems that when TinyCLR hits an error condition (as above) it does not.

ChrisAtSamraksh commented 7 years ago

Strange. I tried to replicate this problem and couldn't.

I purposely made a mismatch in the firmware version to get your error. I used MFDeploy (on Windows 10 with a WLN BTW) and did reboot and stop, and then I erased tinyclr and redeployed a new tinyclr from tinybooter.

Nathan-Stohs commented 7 years ago

I just tried again and couldn't reproduce either. Closing.