HI Dialog Team ,
(1) Maybe this is a stupid doubt ,but still am confused.The OTP memory is 32Kb size right ,so for eg: the hex code in proximity_reporter_fh is nearly 70 kb . So while burning to OTP how it is capable of storing more than the maximum capability ??
(2)So if i need to use external memory instead of OTP ,wat is the minimum range i can choose ? 64Kb or 128Kb or 256 kb ?
(3) What do you mean by OTP header ?
Thankyou
Hi hrq,
the hex file (e.g. 76 KB) is converted on the fly to a binary file. In my case this bin file has a size of 28K.
The hex file contains address information on where to write the code, the bin file doesn't have this.
When using Conn-Manager the hex2bin is creating the bin file which you can find in your working folder.
Best regards, BB_Dialog.
Hi hrq,
2) normally a 128Kbit or 256Kbit memory is used. No restriction on the minimum size, but your code should fit. But small sizes might be hard to find, and even might be more expensive.
3) The OTP header is the part of the OTP that contains information on calibration and trimming, those values are read from OTP during booting.
B.R., BB_Dialog.
Thankyou BB_Dialog !!
So if am using an EEPROM ,while using the Smartsnippet converts the hex to bin and then burns to EEPROM right ?
Hi hrq,
indeed, you can also choose to burn the .bin file if it already exists.
B.R., BB_Dialog
Thankyou BB_Dialog