Hi,
There is one thing I don't understand in OMAP l137 boot, in ARM ubl, I see that u-boot image is copied to External RAM without any modification. Byte-to-byte copy, but U-boot image is an AIS, isn't it ? How can it be executable code ?
BR
Maxime
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.
Hi,
There is one thing I don't understand in OMAP l137 boot, in ARM ubl, I see that u-boot image is copied to External RAM without any modification. Byte-to-byte copy, but U-boot image is an AIS, isn't it ? How can it be executable code ?
BR
Maxime
Yes, that's right, just figured it out.
I'm just wondering, I see in ARM ubl that it reads a header of this binary. Is there a header in every binary ?
I won't be using u-boot but a project I'll have compiled with CCSv4 and then used hex470.exe to make it a binary. Will the binary contain such a header with entry point, app size ... ?
Maxime
The header is added by the flashing utility, either CCS or the serial flashing tool. The binary itself does not have this header and it is added during the flashing process.
Jeff
I'm wondering, is ARM ubl of any use ?
I mean, I can do every initialisation with DSP UBL, then copy ARM code and DSP code at their respective location ... That wouldn't cause any trouble, would it ?
What is the advantages of having an ARM UBL ? Does the DSP have any limitation ?
BR
Maxime
No there is really no point to have an ARM UBL. You can initialize everything in the DSP UBL.
Jeff