We started in 2016 with S7 and S3 µC and developed our own boards, since that we are waiting for an easy to implement and maintainable bootloader/flashloader.
Every time in the last years when I've visited the Renesas booth on embedded world, they guys told me that an useable bootloader framework will be offered in the future.
Then finally when Renesas provides a bootloader/flashloader, Renesas - as far as I know - stopped the support with SSP 1.3.0., why?
May be I'm the only developer, who is confused which bootloader to choose now, ensuring support by Renesas also in future SSP versions.
So I'm not misunderstood, I have to say that I really appreciate SSP and also the support here in RenesasRulz, but regarding the subject bootloader I can't see a really clear and future-proof concept compared to other SSP modules.
E.g. ST provides CAN/Ethernet/USB/UART bootloader versions for their STM32 Cortex M series, why it is not possible to provide something similar for the Synergy family?
Background of this post is, that we actually have to plan a project for huge number of devices, installed all over the country in the next years, but being now unsure which solution we should choose.
What other piece of advice can you give us than to implement the bootloader itself?
Thank you very much and best regards
Attached are flashloader bootloader and downloader projects for the SK-S7G2 and TB-S3A1. Both are blocking using USB-CDC and the transfer interface.
Hopefully they will be useful.
thank you so much for your work and your support. Actually I can successfully program the bootloader and downloader to our custom board. With breakpoints I've verified that the bootloader is called first before jumping to the downloader application with flashing leds.
But now I'm stucking in converting "downloader_usb_cdc_blocking_s3a1_crc.srec" (or should I use the one without crc) file to BCH, the GUI always shows the error message "Error! Please fill in all the information before attempting to convert the script.".
I've attached the screenshot, but I think I've provided all necessary information.
Thanks and best regards
The CRC version of the SREC file is created by an e2studio custom build phase. This can be found in the Builders section of the project's peroperties.
This is only needed when using the debugger and the first build and not when using a free running version of the donloader and/or subsequent builds.
Apologies for not included the newer Python file. Please find it attached. This was modified by another form user, Erik, and fixes an issue where a 4k section of flash can be mistaken for RAM and excluded from the output.