The app I’m working with was using SystemClock.Low, likely persisted on the test unit that I have.
For the sake of testing performance, I switched it to SystemClock.High and from that moment the unit not only stopped working but is now inaccessible. No port in sight from windows nor from TinyCLR config.
I’m using 2.3.0.1000 version of both libs and firmware. SITCore SCM20260E.
I might be wrong, but I remember doing the same on a previous library/firmware version without problems.
Hold ldr pin low and reset to force the board in loader mode. From there, erase all.
1 Like
Not sure if I have access to that in the current unit, but that’s a different problem.
Thanks for the suggestion and we’ll try solving like that.
Still, I’d not expect the board to behave like that. Say that we decide to change the clock in an update in production, and we risk losing the units. I’d expect a change in clock speed transparent and not soft-killing the unit.
Correct. This should not cause any problems. This might just be a coincidence. But if you managed to make it happen again then just let us know how and we will take care of it.
1 Like
Ok. Cannot risk on this unit in these days but as soon as we have another unit we can try on we’ll do. Thanks.