I've tried updating my HP15L (after having successfully done it with my DM41L). It broke off with an error message (which I foolishly failed to record). No beep upon pressing reset.
Now the calc is unresponsive. Doesn't come on. Display stays clear. Tried changing the battery. Battery is full.
Help, please?
[DM15L] Unresponsive after update attempt
Re: [DM15L] Unresponsive after update attempt
Was able to recover the response after I started the sync and pressed reset on the calc:
Code: Select all
Read bootcode version: 2
7
Read part ID: LPC1115.../303, 64 kiB FLASH / 8 kiB SRAM (0x00050080)
Will start programming at Sector 1 if possible, and conclude with Sector 0 to ensure that checksum is written last.
Erasing sector 0 first, to invalidate checksum. Wrong answer on Erase-Command
Re: [DM15L] Unresponsive after update attempt
Never mind... A repeated update has worked. Fresh battery, and a newly downloaded .hex file did the trick.
Feel stupid... maybe the .hex file I used last time was corrupted. Or I did not actually used a fresh battery (I have measured the voltage last time when I put in the battery. It seemed fresh, but voltage alone may not be good enough to indicate. Used a completely new package today.)
Feel stupid... maybe the .hex file I used last time was corrupted. Or I did not actually used a fresh battery (I have measured the voltage last time when I put in the battery. It seemed fresh, but voltage alone may not be good enough to indicate. Used a completely new package today.)
Re: [DM15L] Unresponsive after update attempt
I believe I have read in the forums that the bootstrap firmware update cycle is coded in the base ROM.
These devices should be very hard to brick.
Persistent effort was rewarded
These devices should be very hard to brick.
Persistent effort was rewarded
DM10, DM10L: 00031 / DM11, DM11L: 00112 / DM12, DM12L: 02074
DM15, DM15L: 11069 / DM16. DM16L: 02001 / DM41, DM41L: 00859
DM41X: 00036ß / 00181 DM42: 3108 / 6084 WP43: 0032
DM15, DM15L: 11069 / DM16. DM16L: 02001 / DM41, DM41L: 00859
DM41X: 00036ß / 00181 DM42: 3108 / 6084 WP43: 0032
Re: [DM15L] Unresponsive after update attempt
Just want to apologize that me took it a month to figure out. It was a busy month which left me with not enough patience to do even these simple things which were way down on my priority list.
Re: [DM15L] Unresponsive after update attempt
Had the very same issue last week-end or so while updating both my 41L & 15L.
41L was easy, a real breeze , 15L crashed and looked dead with no more signs of life ....
I even contacted Michael ... that said me to try again with new battery even if mine was still looking good at 2,9V or so.
Then i tried again with a new battery few days later, and 1) the update worked 2) the 15L is back to life.
Conclusion : The Firmware update is very power angry and you need to keep some fresh & good batteries just in case of a crash.
41L was easy, a real breeze , 15L crashed and looked dead with no more signs of life ....
I even contacted Michael ... that said me to try again with new battery even if mine was still looking good at 2,9V or so.
Then i tried again with a new battery few days later, and 1) the update worked 2) the 15L is back to life.
Conclusion : The Firmware update is very power angry and you need to keep some fresh & good batteries just in case of a crash.
DM41L SN01063 - DM42 SN05658 - DM15L SN20438 - DM41X SN00173 - DM16L SN04449
Re: [DM15L] Unresponsive after update attempt
This is exactly what happened to me! Gives me hope that I was not alone!
I did also measured the voltage on the two batteries I tried to use. They looked fine, but broke down very fast. So I suspected a hardware fault, a short maybe, but Michael was adamant that there's just no way a hardware could manifest while updating. Conclusion: it must be the batteries. I do know that voltage is not a perfect indicator for battery capacity, but since it has worked so often and with two batteries here, I refused to accept physical reality.
For other battery types I have a dedicated instrument that measures both voltage and current with some pulse algorithm, but sadly not for CR2032s.
I did also measured the voltage on the two batteries I tried to use. They looked fine, but broke down very fast. So I suspected a hardware fault, a short maybe, but Michael was adamant that there's just no way a hardware could manifest while updating. Conclusion: it must be the batteries. I do know that voltage is not a perfect indicator for battery capacity, but since it has worked so often and with two batteries here, I refused to accept physical reality.
For other battery types I have a dedicated instrument that measures both voltage and current with some pulse algorithm, but sadly not for CR2032s.