AM2434: AM2434BSFFHIALV uart_uniflash.py Incorrect magic number in file header !!!

Hi Martin,

Please refer to thread below. This thread shows a similar issue as yours and the issue was fixed by changing the linker cmd script. 

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1211939/am2432-questions-about-failing-to-use-uart_uniflash-py-with-incorrect-magic-number-error/4572858?tisearch=e2e-sitesearch&keymatch=Incorrect%2520magic%2520number%2520in%2520file%2520header#4572858

Hi,

thank you for the answer. For me is not clear how to solve this. Can you explain me a little bit more the steps?

For me is not clear, if I can use the prebuilt tiimages in C:\ti\mcu_plus_sdk_am243x_08_05_00_24\tools\boot\sbl_prebuilt/am243x-evm/default_sbl_null.cfg because these are for the am243x-evm board. But I have an custom board built similar to the am243x-evm without DDR RAM. Must I build additional boot files?

Is change the devconfig.mak => DEVICE_TYPE?=HS in the SDK. Is this correct?

Please help me I'm not so deep in.

Martin

Hi Martin,

Doesn't your device support HS or FS? Please check the number on your device, the description is on Table 10-1 of datasheet.

Table 10-1. Nomenclature Description

The Link in my previous post mentioned that she changed the DDR to SRM in the liker cmd file.

Does your board use the same flash as the one on TI CC EVM or launchpad? 

Have you tried sbl_uart_uniflash.release.tiimage instead of HS-FS image?

Hi Martin,

The below thread has the similar issue of "incorrect magic number". It might be related to the different flash ID number.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers---internal/f/arm-based-microcontrollers---internal-forum/1222742/mcu-plus-sdk-am263x-uart-uniflash-bootloader-binary-command-never-executes/4618242?tisearch=e2e-sitesearch&keymatch=incorrect%25252520magic%25252520number%25252520AND%25252520header#4618242

Hi QJ (hope this is ok for you),

thank you very much for the help.

- Doesn't your device support HS or FS?

BBBBB => AM2434

r            => B

Z            => S

f             => F

Y            => F

y            => H

t             => I

PPP       => ALV

production code => 709

this looks for me HS type.

- Does your board use the same flash as the one on TI CC EVM or launchpad? 

I use exactly the same OSPI chip as the am243x-EVM board. So CYPRESS 28HS512TAM01.

- Have you tried sbl_uart_uniflash.release.tiimage instead of HS-FS image?

Yes, but in this case I got for Executing command 2 of 2 : 10 times block errors.

Best reagards

Martin

Sorry I forgot the link from your second reply is not accessible..

Regards

Martin

Never mind. The link in my 2nd reply mentioned that "incorrect magic number" was caused by the different flash used on his own board. It is not same as your case. 

I resolved the issue. The root problem was related to my original suspicion that the 25FL256SA has a JEDEC DevID of 0x0219, which is different than the TI Board Default Flash's S25FL128SA. This needs to be accounted for in the SysConfig of the sbl_qspi project which generates a custom .tiimage file. After uploading my custom .tiimage file, the QSPI SBL started to work correctly.

Hi, do you have information on my other reply? I wrote 2 times. Please not misunderstand me. I think I have the HS type. I have no idea how to go forward / solve this problem. The customer is still waiting for my product.

Thanks

Martin

Hi Martin,

It is HS-FS part. My LaunchPad board has a GP chip on it so I cannot test HS-FS mode on it. I will do some other test on my board. 

Hi, I got these data from my chip:

-----------------------
SoC ID Header Info:
-----------------------
NumBlocks            : 2
-----------------------
SoC ID Public ROM Info:
-----------------------
SubBlockId           : 1
SubBlockSize         : 26
DeviceName           : am64x
DeviceType           : HSFS
DMSC ROM Version     : [0, 2, 0, 0]
R5 ROM Version       : [0, 2, 0, 0]
-----------------------
SoC ID Secure ROM Info:
-----------------------
Sec SubBlockId       : 2
Sec SubBlockSize     : 166
Sec Prime            : 0
Sec Key Revision     : 0
Sec Key Count        : 0
Sec TI MPK Hash      : b018658ad99dc903c8c9bfb27b12751099920a042ad1dfea7b7ba57369f15546de285edde6a7b39a8bdc40a27b237f8fb1e57f245e80b929c1e28b024aa2ecc6
Sec Cust MPK Hash    : ad0bc40b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Sec Unique ID        : 40a9e788b802957cff583421fd9b4e86b8e38a79a3e7fcbc8868f535341bbfda

Now I'm wondering. On the Chip it says AM2434 but out : am64x

regards

Martin

Hi Martin,

Have your customer figured out the issue?