topic OTFAD Feature Verification Fail in Kinetis Microcontrollers

OTFAD Feature Verification Fail

dhanapal_rajend — Mon, 24 Sep 2018 07:56:16 GMT

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

Re: OTFAD Feature Verification Fail

jingpan — Tue, 25 Sep 2018 10:02:44 GMT

Hi,

OTFAD is used to cowork with QSPI to decrypt ciphertext stored in external flash. But it seems your bubble demo runs in internal flash. You can see the response to blhost command "Response status = 403 (0x193) QSPI Flash Command Failure".

Regards,

Jing

Re: OTFAD Feature Verification Fail

dhanapal_rajend — Tue, 25 Sep 2018 12:42:08 GMT

Hi Jing,

Following changes already done in linker file to run bubble from QSPI

define symbol m_text_start = 0x68001000;
define symbol m_text_end = 0x69000000;

Flash config area is also changed to select ROM as boot source.

__FlashConfig
DCD 0xFFFFFFFF
DCD 0xFFFFFFFF
DCD 0xFFFFFFFF
DCD 0xFFFFBDFE
__FlashConfig_End

FYI: I have already booted bubble project from QSPI. Please refer the below link.

Success Bubble QSPI link

Regards

R.Dhanapal