Ethernet Flash Boot Loader

Hello Microit,

I developed a simple bootloader application for SK-S7 that uses Ethernet to connect to the TFTP server at 192.168.0.2 (I used TFTPD64 on Windows to host files) and download and program "S7_SK_image.bch". Project was developed for SSP 1.2.0-b.1 and older version of the Flashloader framework but should work with the new modules without any problem.

s7_sk_nx_tftp_boot_1_2_0b1.zip

Regards

Hi Karol,

I got error status = 701 (HEX 0x2bd) at status = g_sf_firmware_image_int.p_api->newImagePrepare what does it mean ?

Can you upload your S7_SK_image.bch file then I can try ?

BR,
James J

Hi JHJ,

We are developing an OTA bootloader, we have also faced the same error (701) while calling newImagePrepare api .
We use 2 slots for our project. We have solved the issue by referring the code shared by Karol.

We used only the sf_firmware_image _internal framework because the downloader framework follows the procedure for
the communication with flashloader utility.

So we have to handle each block separately as the code shared by Karol TFTP bootloader example.

Regards

Hi Karol,

 

Any idea ?

Hi James,

if you have not changed the header location in your program, then try changing 40400 to 40800.
I recommend you to refer flashloader pdf for generation of BCH file and also linker script section.

Regards

Mohammad Hashir

Thanks.
Bootloader works fine now.

Hi Mohammad,

Can you help ?
my board is SK-S7G2.
I am trying to make 2 slots, my first slot is from
FLASH (rx) : ORIGIN = 0x00100000, LENGTH = 0x0180000
1st slot is working fine.

When I try to make
my 2nd slot is from
FLASH (rx) : ORIGIN = 0x00280000, LENGTH = 0x0180000
I got SSP_ERR_INVALID_BCH_DATA.

Hi james,

Are you using bootloader for downloading the new BCH file? If yes then can you please show me how you have setup the configuration for firmware flash internal in bootloader and also in the application code.
Also please tell me how you have created the BCH file?

Regards,

Mohammad Hashir

Hi Mohammad ,

I did not change any bootloader code.

 Setting of Bootloader below:

 

 

My 2nd slot Firmware Image setting below:

Hi james,

Give Address/Pointer for firmware image record to 0x800.
in bootloader client thread change
sf_firmware_image_erase_cfg_t erase_cfg =
{
.slot_number = 0
};
sf_firmware_image_erase_cfg_t erase_cfg =
{
.slot_number = 1
};

also thing to be noted is that the current bootloader code does not search for new images.
so you have to change the configuration.

sf_bootloader_cfg_t my_cfg;

memcpy(&my_cfg, g_sf_bootloader_mcu0.p_cfg, sizeof(my_cfg));
my_cfg.new_image_check = true;

please check these things.

regards

Mohammad Hashir

Hi james

 Just to confirm regarding this image : are debugging two codes at a time?.. please can you tell me whether you are using the TFTP boot example or any other codes? 

regards

Hi james,

For your update, i have finished the OTA for 2 slots by combining both the examples(USB_CDC_blocking and TFTP boot).
I use bootloader code of USB_CDC_blocking example and in application program i added image download and blockWrite method of client_thread_entry which you will get in TFTP_boot example.
In this case Address/Pointer for firmware image record is 0x500.
some changes to noted in boot loader for this case is that:
1)my_entry(g_sf_bootloader_mcu0.p_ctrl, g_sf_bootloader_mcu0.p_cfg, true);//make it true to check new images

2) //comment out 'if' statment and its starting and ending braces in my_entry() for checking new image
// if(check_for_new_images == false)
// {
/** Since we are not checking for new images, only initialize the sf_firmware_mcu_flash interface*/
//ssp_err = g_sf_bootloader_mcu0.p_api->open(p_ctrl, p_cfg, false);
ssp_err = g_sf_bootloader_mcu0.p_api->open(p_ctrl, &my_cfg);

if (ssp_err != SSP_SUCCESS)
{
//break;
}
//ssp_err = 1;
/** Jump to the app */
ssp_err = g_sf_bootloader_mcu0.p_api->appStart(p_ctrl);

if (ssp_err != SSP_SUCCESS)
{
// break;
}

ssp_err = g_sf_bootloader_mcu0.p_api->close(p_ctrl);

return SSP_SUCCESS;
// }

make sure that you have changed the following in application code accordingly:
1) starting address in linker script and clean before build ,
2)slot_number to be erased
3)version number
Its working fine for me.

Best Regards

Mohammad Hashir

Hi james,

For your update, i have finished the OTA for 2 slots by combining both the examples(USB_CDC_blocking and TFTP boot).
I use bootloader code of USB_CDC_blocking example and in application program i added image download and blockWrite method of client_thread_entry which you will get in TFTP_boot example.
In this case Address/Pointer for firmware image record is 0x500.
some changes to noted in boot loader for this case is that:
1)my_entry(g_sf_bootloader_mcu0.p_ctrl, g_sf_bootloader_mcu0.p_cfg, true);//make it true to check new images

2) //comment out 'if' statment and its starting and ending braces in my_entry() for checking new image
// if(check_for_new_images == false)
// {
/** Since we are not checking for new images, only initialize the sf_firmware_mcu_flash interface*/
//ssp_err = g_sf_bootloader_mcu0.p_api->open(p_ctrl, p_cfg, false);
ssp_err = g_sf_bootloader_mcu0.p_api->open(p_ctrl, &my_cfg);

if (ssp_err != SSP_SUCCESS)
{
//break;
}
//ssp_err = 1;
/** Jump to the app */
ssp_err = g_sf_bootloader_mcu0.p_api->appStart(p_ctrl);

if (ssp_err != SSP_SUCCESS)
{
// break;
}

ssp_err = g_sf_bootloader_mcu0.p_api->close(p_ctrl);

return SSP_SUCCESS;
// }

make sure that you have changed the following in application code accordingly:
1) starting address in linker script and clean before build ,
2)slot_number to be erased
3)version number
Its working fine for me.

Best Regards

Mohammad Hashir