All,
Do you have to use new EBOOTXXXX.bin each time you rebuild an OS runtime image or can you stick w/ the ones delivered w/ the BSP package. I'll use BSP 6.13.0 OMAP3503 as an example
BSP - bspdemo_omapwince_06_13_00, comes w/ EBOOTXXXX.bin, NK.bin, XLDRXXXX.bin, and TIEVM3530-XXXX.raw, where XXXX is either NAND, ONENAND, or SD.
When you rebuild OMAP3503 for Debug, there are new 'EBOOTXXXX.bin' files in the \RelDir\TI_EVM_3530_ARMV4I_Debug.
So, can you just use the XLDR + EBOOT (or as its combined into 'TIEVM3530-xxxxxx.raw') from the original BSP 'DEMO' install?
Also, say one wants to use Platform Builder to download/re-flash XLDR or EBOOT - how do you do this? I only see examples of using PB to load NK.bin automatically when you connect and reboot the EVM.
Thanks.
Marc,
1. There are some cases where you have to use the .raw file that is generated with your build and reflash. (I think the .raw files are only generated for retail builds.)
Other than these conditions if you are not making changes to bootloader files you should be fine not flashing. If in doubt use the files generated as part of your build instead of using the files that came with the BSP package.
2. We typically use the EVM flash utility that comes with the BSP package (both src and demo) to flash the .raw file.
There is a way to do it with PB also. Under Project->Propeties->Configuration Properties->General there is a pull down menu for "Target filename for debugger". Here you can select the appropriate .bin file (default is NK.bin). Rest of the procedure is same as what you would follow for NK.bin. (You will also have to enable the check mark for "Write Runtime image to flash memory" under Project->Propeties->Configuration Properties->Build options and Make runtime image etc).
Jatin
---