This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA2PXEVM: Could i select Appimage in Bootloader?

Part Number: TDA2PXEVM

Hello, 

Processor : TDA2PX

SDK : VisionSDK_03_08

I want select Appimage when booting

so, I writed appimages both 0x80000 and 0x120000 in qspi 

and i modified appimage address select possible by UART

but only appimage writed second can boot.

for example, if i write 0x80000 and 0x120000, 0x120000 can boot only

if i write 0x120000 and 0x8000, 0x80000 can boot only

first writed appimge occur "Invalid Magic String in MultiCore Image" error

select Appimage in Bootloader is possible??

Please give me advice

================ log =====================

TDA2Px SBL Boot

DPLL Configuration Completed

Clock Domain Configuration Completed

Module Enable Configuration Completed

TI EVM PAD Config Completed

TDA2Px NEW DDR Configuration Config Start...........

TDA2Px DDR Configuration
>> START ==> Overall DDR configuration
>> START ==> EMIF1 and EMIF1 DDR IOs config (CTRL_MODULE_CORE_PAD module)
Launch full leveling
Updating slave ratios in PHY_STATUSx registers
as per HW leveling output
HW leveling is now disabled. Using slave ratios from
PHY_STATUSx registers
One EMIF - 512MB total memory
Same memory mapped at 0x80000000 and 0xA0000000
>> END ==> overall DDR configuration completed / DDR memory can now be accessed

DDR Config Completed

App Image Download Begins

Manufacturer ID -

Device ID - 
ENTER THE APPIMAGE TO BE LOADED:
0: 0x80000
1: 0x100000
2: 0x120000
3: 0x140000
4: 0x160000

APPIMAGE ADDR : 0x00120000U
currAppImageAddr before :
0x120000
magicStrHdrStart :
0x254534d
magicStr :
0x0
currAppImageAddr after :
0x12001c
Invalid Magic String in MultiCore Image v2

Valid App Image is not Available

Putting MPU CPU1 in Off mode

*****************************************************************

PMCCNTR counts once every 64 clock cycles, multiple by 64 to get actual CPU cycles

SBL Initial Config Cycles - 118406 (10.10 ms)
SOC Init Cycles - 170647 (14.56 ms)
DDR Config Clock Cycles - 658141 (56.16 ms)
App Image Load Cycles - 102213915 (8722.25 ms)
Slave Core Bootup Cycles - 53907 (4.60 ms)
SBL Boot-up Cycles - 103216072 (8807.77 ms)
Time at which SBL started IPU1_0 - 289725 (8841.70 ms)
*****************************************************************

Putting MPU in Retention...

====================================================

Regards,