Flashloader_pack1.X.0.exe

Hi victor,

For SSP 1.3.0 there is a newer version of the Flashloader Framework - v1.1.0. You will find the framework in the Synergy Gallery: synergygallery.renesas.com/.../utility

The downloaded archive contains .exe installer in Flashloader_DK-S7G2\Flashloader_Module, which will install the .pack file for the selected e2 Studio instance. There is also the .pack file without an installer.

Regards,
adboc

Hi

I am also looking for Flashloader_pack1.3.0.exe - can anyone tell me where it is currently at

many thanks,
alan..

I made that I described above and I restarted e2 studio, I can see now Flashloader in Threads tab > New Stack > Renesas .
However there are only three possibilities and not the one I used in Renesas.Synergy_flashloader.1.3.0.pack . Bootloader Framework on sf_bootloader_mcu is missing in Renesas.Synergy_flashloader.1.4.0.pack
Does anyone have a suggestion?

Hi Bj,

Sorry, you're right, it's needed to rename *.pack.zip to *.pack and place it in packs/.

I've just created a new project and see the Bootloader Framework on sf_bootloader_mcu available. Have you selected SSP 1.4.0 in BSP tab?

Regards,
adboc

Hi adboc,

Thanks for your help, I also tried with a new project and I could see all modules. However, I couldn't see them in my existing project so I deleted it from my workspace and imported it again.

When I opened my project and built with SSP 1.4.0, it didn't remove bootloader component (certainly because the pack is recognized) and the build is ok.

However I still can't see all modules in Flashloader but my project works, it's not a problem for now but I can't add some modules if needed.

Thanks,

Bj

Hi Bj,

Could you check if there are no components from SSP older than 1.4.0 in Components tab? I suggest removing .module_descriptions directory, it will be generated again when opening the project.

Regards,
adboc

Hi Adboc,

I checked and all components come from SSP 1.4.0. I did what you suggested by removing .module_descriptions directory, when I opened the project it generated again the directory but I couldn't see the flashloader module in Threads tab > New Stack

Regards,
Bj

Hi All,

As I said above, it works for one of my projects but I can't see all the modules in Threads tab > New Stack > Renesas. That's not a problem for this project, however I need to add a module to another existing project and I can't.

In the C:\Renesas\e2_studio_6_2_0\internal\projectgen\arm\packs there is the Renesas.Synergy_flashloader.1.4.0.pack. I tried to remove it and add it again, the change has been detected in e2Studio but I have this message:
"Installing Synergy support files: Renesas.Synergy_flashloader.1.4.0.pack... No support files present."

Regards,

Bj

Hi All,

As I said above, the first time I moved to the SSP 1.4.0, in my existing project which uses the Bootloader the module has been removed. I added the Renesas.Synergy_flashloader.1.4.0.pack and when I opened the project again module was present and it built. However I can't see all the modules which are contained in the pack.

Now, I have to add the sf_firmware_image and the sf_memory_mcu_flash in another project. I can see the module I need, I Added it and maked a generate project content. It seems there is a problem when the generate project content is done because there is no renesas content which is created in sysnergy folder of my project.
As there is no .c and .h files the build failed.
To make the build work, I have to add manually the renesas folder in synergy folder. I still don't understand why i can't see all the modules and why it does'nt work when I generated project content.

Regards,
Bj

Hi Bj,

Were you able to resolve this issue? I'm having similar problems. I am not able to see the framework modules whether it's in a new project or an existing project. I am using ssp 1.5.0-rc.1.

Hi AJ,

As of SSP 1.5.0 the Flashloader Framework is no longer maintained in favour of the Secure Boot Manager that will be qualified and released in the near future. You can change pdsc contents and xml file names inside the pack to make it discoverable under SSP 1.5.0: Renesas.Synergy_flashloader.1.5.0-rc.1.pack.zip. You will need to unzip this first before doing Import -> CMSIS Pack.

Regards

Hi Karol,

Thanks a lot. I could see the frameworks now after creating a new project.

Regards,
AJ

Hi Karol,

Thanks a lot. I could see the frameworks now after creating a new project.

Regards,
AJ

Hi Karol,

I tried to see if I could compile the sample programs mentioned in the app note here R11AN0073EU0110 Customizable Flashloader Solution for Synergy MCUs

I imported the bootloader and downloader projects and converted to ssp 1.5.0-rc.1. However, when I comipiled I got tons of errors. I was under the impression that since I was able to get the flash loader pack in successfully, i shouldnt have any problems.. After building the bootloade_usb-cdc_blocking, I got this message in the console. Any idea why it's not compiling?

Thanks.
AJ


16:45:42 **** Incremental Build of configuration Debug for project bootloader_usb_cdc_blocking ****
make -j8 all
'Building file: ../src/hal_entry.c'
'Invoking: Cross ARM C Compiler'
C:\Renesas\e2_studio\eclipse\../Utilities/isdebuild arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -O2 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wunused -Wuninitialized -Wall -Wextra -Wmissing-declarations -Wconversion -Wpointer-arith -Wshadow -Wlogical-op -Waggregate-return -Wfloat-equal -g3 -D_RENESAS_SYNERGY_ -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy_cfg\ssp_cfg\bsp" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy_cfg\ssp_cfg\driver" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\ssp\inc" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\ssp\inc\bsp" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\ssp\inc\bsp\cmsis\Include" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\ssp\inc\driver\api" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\ssp\inc\driver\instances" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\src" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\src\synergy_gen" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy_cfg\ssp_cfg\framework" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\renesas\flashloader\src\sf_bootloader" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\renesas\flashloader\inc\api" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\renesas\flashloader\inc\instances" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\renesas\flashloader\src\sf_firmware_image" -I"C:\Albert\Projects\MCU\S7G2\Westnet\bootloader_usb_cdc_blocking\synergy\renesas\flashloader\src\sf_memory_mcu_flash" -std=c99 -MMD -MP -MF"src/hal_entry.d" -MT"src/hal_entry.o" -c -o "src/hal_entry.o" -x c "../src/hal_entry.c"
../src/hal_entry.c:5:21: error: unknown type name 'sf_bootloader_ctrl_t'
ssp_err_t my_entry (sf_bootloader_ctrl_t * const p_ctrl, sf_bootloader_cfg_t const * const p_cfg, bool check_for_new_images);
^
../src/hal_entry.c:5:58: error: unknown type name 'sf_bootloader_cfg_t'
ssp_err_t my_entry (sf_bootloader_ctrl_t * const p_ctrl, sf_bootloader_cfg_t const * const p_cfg, bool check_for_new_images);
^
../src/hal_entry.c: In function 'hal_entry':
../src/hal_entry.c:49:9: warning: implicit declaration of function 'my_entry' [-Wimplicit-function-declaration]
my_entry(g_sf_bootloader_mcu0.p_ctrl, g_sf_bootloader_mcu0.p_cfg, false);
^
../src/hal_entry.c:49:18: error: 'g_sf_bootloader_mcu0' undeclared (first use in this function)
my_entry(g_sf_bootloader_mcu0.p_ctrl, g_sf_bootloader_mcu0.p_cfg, false);
^
../src/hal_entry.c:49:18: note: each undeclared identifier is reported only once for each function it appears in
../src/hal_entry.c: At top level:
../src/hal_entry.c:73:21: error: unknown type name 'sf_bootloader_ctrl_t'
ssp_err_t my_entry (sf_bootloader_ctrl_t * const p_ctrl, sf_bootloader_cfg_t const * const p_cfg, bool check_for_new_images)
^
../src/hal_entry.c:73:58: error: unknown type name 'sf_bootloader_cfg_t'
ssp_err_t my_entry (sf_bootloader_ctrl_t * const p_ctrl, sf_bootloader_cfg_t const * const p_cfg, bool check_for_new_images)
^
make: *** [src/hal_entry.o] Error 1
src/subdir.mk:18: recipe for target 'src/hal_entry.o' failed

16:45:43 Build Failed. 7 errors, 2 warnings. (took 971ms)

Hi AJ,

Have you imported these projects before or after flashloader pack has been added? I highly recommend restarting e2studio and creating a New Synergy Project to force pack discovery before importing older flashloader examples.

Regards

Hi Karol,

I was able to make it work. I did everything again but this time I ran the Flashloader_pack_1.3.0.exe first. It installed something. Then I CMSIS imported the 1.5 pack you sent me, updated the SSP ver from 1.3 to 1.5. I was able to see the framework blocks on the configurator. I clicked build and it worked for both bootloader an downloader.

Another question. How do I launch flashloader utility GUI. I installed the python files required but I can't find the GUI anywhere.

Thanks.
AJ

My Apologies Karol. I found it. It was included in the flashloader folder. I thought it was installed elsewhere.


Thank you for all your help.

AJ

Hi Karol,

I followed the steps mentioned in this thread for ssp 1.5.0-r.c.1

and I took the 'Renesas.Synergy_flashloader.1.5.0-rc.1.pack.zip ' file, unzipped it and put it under following path
'C:\Renesas\Synergy\e2studio_v6.2.1_ssp_v1.5.0\internal\projectgen\arm\packs'. I tried to get the 'USB CDC blocker bootloader and downloader' from the application project 'an-r11an0073eu0111-synergy-ssp-flashloader' working on ssp 1.5.0.

I Re-created everything from the application project for 'USB CDC blocker bootloader and downloader' in a new project and managed it to compile and program the target DK-S7G2 board through JTAG. However when I execute the code I am getting the following error when it tries to open the downloader API
'err = g_sf_downloader0.p_api->open(g_sf_downloader0.p_ctrl, g_sf_downloader0.p_cfg);'.

The error message is 'SSP_ERR_INTERNAL - Unexpected size format from backend: 4'.

when I dig further down I found the error happen in the following line

if ((p_cfg->memory_type == SF_FIRMWARE_IMAGE_MEMORY_TYPE_BCH))

of the "ssp_err_t SF_FIRMWARE_IMAGE_open (sf_firmware_image_ctrl_t * const p_api_ctrl,
sf_firmware_image_cfg_t const * const p_cfg)" function.


The memory type configured my project is ' SF_FIRMWARE_IMAGE_MEMORY_TYPE_RAW' and it expects it to be in 'SF_FIRMWARE_IMAGE_MEMORY_TYPE_BCH' format.

Also, I tried importing the SSP 1.3.0 application project to SSP 1.5.0. I got imported and I was able to compile the project. When I tries to debug the project it come up with an error saying the break point is beyond maximum target address.

Note: The things which I notice in my environment which could lead to this problem are

1. I am using SSP 1.5.0 and the pack file given is for 1.5.0-rc.1
2. In the configuration page under the 'BSP' tab I have a warning symbol(!) against SSP version saying 'Warning: Some selected component do not match this SSP version'.
3. And, I don't know any exclusive process to import the 'Renesas.Synergy_flashloader.1.5.0-rc.1.pack.zip' to CMSIS pack. As I mentioned above I just pasted the
'Renesas.Synergy_flashloader.1.5.0-rc.1.pack' file to 'C:\Renesas\Synergy\e2studio_v6.2.1_ssp_v1.5.0\internal\projectgen\arm\packs' other than that I haven't done anything else to import.

Please reply.

Regards
Sheik

^Same as Sheik

I would also like help using the 1.5.0 secure boot loader.

Board: S7G2 SK
Device: R7FS7G27H3A01CFC
Toolchain: GCC ARM Embedded
Toolchain Version: 4.9.3.20150529
SSP Version: 1.5.3

So far, I think I did everything right, but I dont see the stack available from the menus, and I have not found any example projects.

OK, I have installed the pack, and it shows up in the stack menu. Is there an example project?