AnsweredAssumed Answered

OTFAD Feature Verification Fail

Question asked by dhanapal rajendran on Sep 24, 2018
Latest reply on Sep 25, 2018 by dhanapal rajendran

I am using FRDMK82F board. I am trying to check the OTFAD feature.

 

1. I have used Bubble project and changed the linker file settings as follows

define symbol m_interrupts_start = 0x0000A000;
define symbol m_interrupts_end = 0x0000A3BF;

define symbol m_bootloader_config_start = 0x0000A3C0;
define symbol m_bootloader_config_end = 0x0000A3FF;

define symbol m_flash_config_start = 0x0000A400;
define symbol m_flash_config_end = 0x0000A40F;


Generated .srec file and processed .srec file using otfad.py file using python and output is 

 

"C:\Python27>python otfad.py K82_bubble_A000.srec K82_bubble_A000_otfad.srec
1056
Processing successfully!"

 

2. In "factory_otfad.bd" file boot_sec_init and boot_sec_progress changes done. Using elftosb sb file is generated. Below is the command.

"elftosb -V -c factory_otfad.bd -o K82_bubble_A000_otfad.sb"

 

3. K82_bubble_A000_otfad.sb file is loaded and the output is 

 

blhost -u -- receive-sb-file K82_bubble_A000_otfad.sb
Inject command 'receive-sb-file'
Preparing to send 19040 (0x4a60) bytes to the target.
Successful generic response to command 'receive-sb-file'
(1/1)6%usb hid detected receiver data abort
Data phase write aborted by status 0x2712 kStatus_AbortDataPhase
Possible JUMP or RESET command received.
Response status = 403 (0x193) QSPI Flash Command Failure.
Wrote 1216 of 19040 bytes.

 

factory_otfad.bd(this file is causing the issue,needs some update) and log file is attached for reference.

 

Need support for this issue.

 

Thanks and Regards

R.Dhanapal

Outcomes