• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 532 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

[FAQ] PROCESSOR-SDK-AM64X: AM64x/AM243x SR 2.0 Device Type Transition

PROCESSOR-SDK-AM64X: MCU-PLUS-SDK-AM64X

True Loan
Prodigy 212 points
Part Number: PROCESSOR-SDK-AM64X
Other Parts Discussed in Thread: SYSCONFIG

Working with v08.06.00.43 using a SR1.0 (DEVICE_TYPE=GP) custom board

I can successfully boot this hardware using an SD Card with a FAT partition with the following on it: tools\boot\sbl_prebuilt\am64x-evm\sbl_null.release.tiimage 

I want to rebuild the sbl_null example with my own DDR timings (which have been verified to work using a different OS), which I have already provisioned in drivers\ddr\v0\soc\am64x_am243x\board_ddrReginit.h

When I import the sbl_null example (without making any changes) and build the example, I only get the following in my workspace:

I cannot boot the resulting tiboot3.bin from an SD Card using my SR1.0 hardware and I think its because CCS is assuming DEVICE_TYPE=HS (I dont see a sbl_null.Release.tiimage like I would expect, only the sbl_null.Release.hs_fs.tiimage)

My question is, how do I build specifically for DEVICE_TYPE=GP? Or force those GP binaries to be built along with the HS-FS binaries?

Some thoughts and observations  I have (sharing in case it helps):

  • The HS FS Migration Guide for v08.06.00.43 seems to imply that both DEVICE_TYPEs should be built without having to pass any extra arguments
  • devconfig\devconfig.mak seems to have "DEVICE_TYPE?=GP" already set
  • 0
    Prodigy 212 points

    I think I have a partial workaround, sharing for others. I would still appreciate a TI expert weighing in.

    I still can't get sbl_null.Release.tiimage to be built/deployed alongside sbl_null.Release.hs_fs.tiimage, but I was able to get the sbl_null.Release.hs_fs.tiimage to boot on my SR1.0 hardware by disabling "Application Image is X509 Signed" in the BOOTLOADER driver settings within Sysconfig.

    • Note that disabling "Application Image is X509 Signed" using the "Debug" build configuration didn't seem to work. I only had success with the Release config.
    • My sbl_null.Release.hs_fs.tiimage with "Application Image is X509 Signed" disabled boots BUT it takes about 40 seconds to give you the expected output on the console, ie:
      Starting NULL Bootloader ...

DMSC Firmware Version 8.6.4--v08.06.04 (Chill Capybar
DMSC Firmware revision 0x8
DMSC ABI revision 3.1

INFO: Bootloader_runCpu:155: CPU r5f1-0  is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU r5f1-1 is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU m4f0-0 is initialized to 400000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU a530-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU a530-1 is initialized to 800000000 Hz !!!
INFO: Bootloader_loadSelfCpu:207: CPU r5f0-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_loadSelfCpu:207: CPU r5f0-1 is initialized to 800000000 Hz !!!
INFO: Bootloader_runSelfCpu:217: All done, reseting self ...

      whereas tools\boot\sbl_prebuilt\am64x-evm\sbl_null.release.tiimage starts up and gives you the same output instantly.
  • +1 in reply to True Loan
    TI__Guru 69541 points

    Hello True,

    The CCS builds also generate the GP images and they are identified with the .tiimage extensions. So, the image you are looking for is named sbl_null_am64x-evm_r5fss0-0_nortos_ti-arm-clang.tiimage.

    Regards,

    Prashant