Hello,
I have one question regarding the file programmer_es5.bin, mentioned in the AN-B-020.
I'm using a PAN1740 module and I need to burn custom firmware in its OTP. I have sucessfully established UART communication between SmartSnippets and the module, since I can load the firmware through the booter funcionality.
Before burning the OTP, I've checked guidelines provided on a couple forum posts, but I found out there was a lot of bits which were either missing or shifted. These errors, despite present all over the code, did not add up throughout the burning process, as I'd expect if it was simply a timing issue. This is clear because there are still sections from later parts of memory which were correctly burned.
These are the guidelines followed:
>https://support.dialog-semiconductor.com/can-you-please-provide-guides-b...
>https://support.dialog-semiconductor.com/step-step-guidelines-programmin...
Checking the AN-B-020, which describes the process for recording UART via CLI, I noticed that the file programmer_ES5.bin needs to be recorded before the OTP burning procedure. Is this firmware required to correctly burn the OTP through SmartSnippets, or is it only used in the CLI method? Is it loaded automatically when using SmartSnippets or do I need to manually load it through the booter before sending the command to burn the OTP?
I'm not sure this has anything to do with the issue I had, but its an open possibility which I'd like cleared up.
Best Regards,
Felipe Ferrazzi
tl;dr: Do I need to load programmer_es5.bin through booter before burning the OTP if I'm using Smart Snippets instead of CLI?
Hi felipe.ferrazzi
你能澄清SmartSni的哪个版本吗ppets you are using? Probably, the programmer_ES5.bin is for a previous version of SmartSnippets, because I can’t find it in installation folder in version 4.8.3. Also, the SmartSnippets loads automatically the files that are necessary and they are located in the installation folder.
Thanks, PM_Dialog
Hello, thanks for the quick reply.
Okay, I checked the software version and turns out I used v3.7.
I found the programmer_ES5.bin file in "C:\Users\(username)\Documents\resources" directory, which seems to be generated by SmartSnippets.
It is not completely in accordance to the one described in AN-B-020, but it's close enough.
The AN states the file can be found at c:\Users\your_name\SmartSnippets\resources\programmer_ES5.bin, but this directory isnt present on my system.
Can you confirm whether v3.7 requires the manual loading of the programmer firmware via Smart Snippets, or was this functionality was only added on more recent versions? I'll update de software but this might help with figuring out the reason behind this issue.
Best Regards,
Felipe
Hi felipe.ferrazzi,
The Smart Snippets that you are using is obsolete, yes the Smart Snippets will automatically download a fw which acts as a programmer in order to interact with the Smart Snippets tool as soon as you hit the connect (in case you would like to interact with the OTP or the Flash). If you are using the CLI and not the GUI then you need to download explictly the programmer, (in such an old version as 3.7 the name of the programmer should be programmer_ES5.bin but in newer versions the name is jtag_programmer.bin or flash_programmer for the UART interface). When using the CLI when the command requires a fw to be downloaded first the command provides a parameters named [-firmware firmware_file], please check the help menu option in the Smart Snippets Toolbox and check how to use the CLI commands from either the pdf of the html help guide version.
Thanks MT_dialog