NP-41 Emulator (may be)

[Chris Chung]

(03-17-2018 01:54 PM)Massimo Gnerucci Wrote:  Alas Chris, I think I finally bricked it.
This morning I started upgrading a DM42, then a 39GS with newRPL and, finally my NP-41. The first two went well, but not the third.

Well, too many different procedures to follow for an aged brain, it seems...

After connecting the unit to the PC via USB and Teraterm I uploaded the new firmware (or I think I did), now all I have on the display is "NP41 =2432" no matter what key combination I try.

Let me know, please, if there's something I can try, otherwise I'll wait for a new board revision and order it, if/when available.

Keep up the good work!

Massimo, the recurring display of NP41 = xxxx means your unit is stuck at startup (reading the battery voltage). It may also be resetting itself if the XXXX voltage value changes intermittently.

If the key test fails, i.e. key press does not show key value, there is a chance that the key scanning lines got shorted, although this is not likely. However, this could also prohibit you to enter bootloader mode when / if the key scan H/W fails.

Another possibility is that the battery had drained too much and the unit cannot continue further when certain peripherals are required (like FRAM access need certain voltage). You may try a fresh battery but it may not solve the problem totally. When battery drained like that fast, that means problem w/ the H/W or PCB. I had some units assembled and runs well, and put in sleep (turn off), they would act up after some hours / days and take 10+mA, resets itself etc. The normal operating current for a good unit is about 1.2mA (1.5mA when doing key test) and 0.6uA during sleep.

The bootloader should still be working. You may want to try to re-do the firmware update and see if it can be unbricked.

Otherwise you will have to wait again.

+rprosperi, +smp

I am still working on the final design, working on the last 10% of traces, plue the key legend silkscreen. The old S/W I used only goes to 8 mils traces. I am using a better S/W that can do 6 mils traces. Not sure the trace width had caused all these intermittent problem, but got to try anyway.