AWR6843AOP: Issue in running the image from Ext. Flash to RAM, after successful copy of image from Ext. Flash

Md Abul Fazal

Part Number: AWR6843AOP

Scenario 1 - I have a customized bootloader for downloading appl image. After successful download and Copy of appl image to RAM a soft reset is performed.

But after the softreset the appl code doesn't runs.

I have a radar appl final *.bin file. I have generated a corresponding *.hex file with an offset added to the memory locations using srec_cat.exe

srec_cat.exe appl.bin -Binary -offset 0xC010000 -o appl.hex -Intel where 0xC010000 is the appl start address of ext. flash.

Here the new appl does't run after successful copy to RAM

Scenario 2 -

Actually the catch is that I have another appl with only MSS code.

*.hex generation using -

srec_cat.exe appl.bin -Binary -offset 0xC010000 -o appl.hex -Intel where 0xC010000 is the appl start address of ext. flash.

Here the new appl run after successful copy to RAM.

Am I missing something in the scenario 1???

Please tell.....

over 3 years ago

0 Md Abul Fazal over 3 years ago

Prodigy 130 points

Hello everyone, Could anyone please tell what I might be missing here??

Regards,

Abul

0 Sudharshan KN over 3 years ago in reply to Md Abul Fazal

TI__Genius 10550 points

Hi,

What is the difference between the first method and second one. The command pasted seems to be the same. is there a difference in the implementation of the application code? Please let us know.

Regards,

Sudharshan K N

0 Md Abul Fazal over 3 years ago in reply to Sudharshan KN

Prodigy 130 points

yes the application is different in both . On first scenario bootloader has only mss code but in second scenario has both dss and mss code.The final bin file generated in second scenario has been used here ( srec_cat.exe appl.bin -Binary -offset 0xC010000 -o appl.hex -Intel where 0xC010000 is the appl start address of ext. flash. ).

0 Sudharshan KN over 3 years ago in reply to Md Abul Fazal

TI__Genius 10550 points

Hi,

Let me check if we need to have a different configuration for the image generation for both the cases.

Regards,

Sudharshan K N

0 Md Abul Fazal over 3 years ago in reply to Sudharshan KN

Prodigy 130 points

In my last reply i mentioned it otherwise,

Scenario1 - has both dss and mss code.The final bin file generated in here has been converted to *.hex format using srec_cat.exe ( srec_cat.exe appl.bin -Binary -offset 0xC010000 -o appl.hex -Intel where 0xC010000 is the application start address of ext. flash). In this case after copy of application Image from ext. Flash the application doesn't run.

Scenario2 - has only mss code.The bin file is converted same way. But in this case after copy of application Image from ext. Flash the application(with only mss code) runs properly.

Please check once , thanks in advance

Regards,

Abul

0 Md Abul Fazal over 3 years ago in reply to Sudharshan KN

Prodigy 130 points

Hi Sudharshan KN

Did you find anything in this issue?

Thanks & Regards,

Abul

0 Sudharshan KN over 3 years ago in reply to Md Abul Fazal

TI__Genius 10550 points

Hi,

I am still looking into this and will get back to you on the same.

Regards,

Sudharshan K N

0 Sudharshan KN over 3 years ago in reply to Sudharshan KN

TI__Genius 10550 points

Hi,

The document located in the image create folder mmwave_sdk_03_05_00_04\packages\scripts\ImageCreator of SDK has the user guide "Image_Creator_User_Guide.pdf" for creating the multicore and single core images. Please refer to the same for details.

Regards,

Sudharshan K N

Sensors

Sensors forum

AWR6843AOP: Issue in running the image from Ext. Flash to RAM, after successful copy of image from Ext. Flash