I'm finishing a project with a RX24T device and the E2Studio. Right now I have to protect my work. For this reason I would like to activate the ID code in order to avoid the copy firmware.
I have activated the " ROM Code Protection" and the " ID Code Protection", but unfortunately seems that the debugger sessions just update the first.
Please have a look :
Could be that the debugger sessions doesn't work with the "ID Code Protection" feature?
Thansk a lot
This thread answers your question: https://community.renesas.com/mcu-mpu/rx/f/rx-forum/4693/e2studio-id-code-rx
JBIf this response, or one provided by another user, answers your question, please verify the answer. Thank you!Renesas Engineering Community Moderatorhttps://community.renesas.com/https://academy.renesas.com/https://en-support.renesas.com/knowledgeBase/
Thanks for your quick answer. Now I can access the flash ID code even debugging with the parameters "Write On Chip Flash Memory". Thanks.
Now, I have to ensure that; without ID code I can read the content. And with ID code I can't. Achieving that I could send the firmware wherever with the ID code enable of course.
So In this way, let's check the protection disable, or NO ID code, or ID code set to 0xFF; all the same:
I have compiled the firmware with all ID code set to 0xFF, and UNFORTUNATELY I can't read the memo content. The read file generated by RFP is all set to 0xFF. I'm going to explain:
Have a look to his picture:
- compiled file .mot: you can see all the "random" values. Note that the ID code is set to 0xFF.
- I program with RFP
- After I read de memory via menu: "target Device" and "Read Memory...." and the .mot generated content ALL 0xFF
I expect read the real memory content; I mean all the random values just the same that the .mot generated by the compiler.
Seems that I'm erasing the microcontroller, but I don't know how?
What do you think?
Thanks a lot in advance.
What do you tell me?
Why with all the ID code set to 0xFF, I can NOT read the memory content?
Thanks for your time.
I have been investigating and finally I have fixed it.
Have been my fail. Conclusions:
- On debug sessions seems no ID code is update, nevertheless is evaluated.
- Be ware with the endian format on ID code. Its easy to fail on the Control Code byte position. If this occurs then the flash is always erased and the RenesasFlashProgrammer give a ID warning with disable IDCode, just because has been erased previously!!!
So, at the end, Renesas, works as expected.
Thanks a lot