Author Topic: How do we know if software has way too many EEPROM writes?  (Read 10595 times)

0 Members and 1 Guest are viewing this topic.

Offline TomS_

  • Frequent Contributor
  • **
  • Posts: 834
  • Country: gb
Re: How do we know if software has way too many EEPROM writes?
« Reply #75 on: February 13, 2018, 02:14:37 pm »
Easiest way to get thanks on the EEVblog forum .. respond to a treez thread.

Seriously, what is with that? Even posts that seem to criticise and poke fun get thanks!!? :wtf:
 
The following users thanked this post: ocset

Offline 3db

  • Frequent Contributor
  • **
  • Posts: 331
  • Country: gb
Re: How do we know if software has way too many EEPROM writes?
« Reply #76 on: February 14, 2018, 10:48:43 am »
:TomS_
Even your one.   :-DD
 
The following users thanked this post: TomS_, ocset

Offline bson

  • Supporter
  • ****
  • Posts: 2265
  • Country: us
Re: How do we know if software has way too many EEPROM writes?
« Reply #77 on: February 14, 2018, 11:01:01 pm »
To answer the original question, if you have a hardware debugger and can access the chip with it, you can disassemble enough to find the EEPROM writing code and set a hw breakpoint there.  Configure the breakpoint to automatically resume and use it to count the number of times that code is executed.  If fusing prevents access, see if you can find a copy of the binary/hex/elf file that gets programmed and program it yourself to a blank device using the debugger, then find the EEPROM write code and count using a breakpoint.  If it needs to run on the actual board just reflow your own unfused and accessible one onto it.

 
The following users thanked this post: ocset


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf