• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 132 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.

SK-AM62-LP: TEye ramtest on HS_FS device

Frederik Hansen
Prodigy 60 points

Part Number: SK-AM62-LP
Other Parts Discussed in Thread: AM62P

I am trying to run the Teye ram test on the SK-AM62-LP devboard made by mistralsolutions, and i am having an issue with getting the Teye ramtest from the MCU_SDK to work.

i have packages the appimage according to the readme.txt and signed it with the appimage_x509_cert_gen.py file in the tool/boot folder and the app_degenerateKey.pem fount in the tools/boot/signing folder.

I have done this for both the mcu_plus_sdk_am62x_11_01_00_16 and the mcluplus_sdk_am62x_11_02_00_23 SDKs 

i have then tried booting the resulting appimage with the command described in the readme

 


python uart_bootloader.py -p COMx --bootloader=sbl_prebuilt/am62ax-sk/sbl_uart.release.tiimage 
                                                 --file=sbl_prebuilt/am62ax-sk/sbl_null.release.tiimage
                                                 --file=../../tools/boot/AM62A_AM62P_TEye_A53_read_unsigned.appimage

i have also tried creating my own .cfg file with the same files an booting with that. On top of this i have tried booting the appimage from the SD card.

 

None of these methods have worked, and have either resulted in nothing in the terminal, or the following terminal output.

liaf.png

 

I have run out of ideas to get this working.

  • 0
    TI__Expert 7255 points

    Greetings Frederik,

    Just double checking, are you using the correct version of the firmware? The AM62A_AM62P version will not work on AM62X (the X is more for a number than another letter).

    Sincerely,

    Lucas

  • 0 in reply to Lucas Bowe
    TI__Expert 7255 points

    Greetings Frederik,

    I was able to briefly borrow an AM62x EVM to check this. It seems for the AM62x MCU+SDK the loading sequence is a little different. The version I had on the PC while I was using the board was 11.0.0.16 but this should work on any version barring minor differences. 

    Can you try the following steps:

    1. Create a config file (name can be anything) under sbl_prebuilt/am62x-sk-lp. This seems to be important, as trying the command line approach to the script causes it not to recognize
      1. Contents are: 
        # First point to sbl_uart binary, which function's as a server to receive application images of other cores through uart
--bootloader=sbl_prebuilt/am62x-sk-lp/sbl_uart.release.hs_fs.tiimage

# This is example appimage which will be loaded to the M4 core
--file=../../examples/hello_world/am62x-sk-lp/m4fss0-0_nortos/ti-arm-clang/hello_world.release.appimage.hs_fs

# This is example appimage which will be loaded to the a53 core
--file=./AM62X_TEye_A53_read_signed.appimage


    2. If you have not already, compile the hello world m4 nortos example project under examples/hello_world/am62x-sk-lp/m4fss0-0_nortos/ti-arm-clang/hello_world.release.appimage.hs_fs
      1. If you are in the tools/boot directory, this will work: 
        gmake -C ..\..\examples\hello_world\am62x-sk-lp\m4fss0-0_nortos\ti-arm-clang\


    3. For creating the rprc image, there seems to be another argument in the recent version of the SDK called SW_VERSION. This value can be found under the imports.mak file in the root of the SDK, for the version I had it was 0x0B000010
      1. The rprc image generation I used was this: 
        node .\out2rprc\elf2rprc.js .\AM62X_TEye_A53_read.out 0x0B000010
      2. The multicore image generation is the same
      3. For signing an HS-FS device, I followed the guidance in the SDK documentation. The command I used was this: 
        python .\signing\appimage_x509_cert_gen.py --bin .\AM62X_TEye_A53_read_unsigned.appimage --authtype 0 --loadaddr 84000000 --key .\signing\app_degenerateKey.pem --keyversion 1.5 --output .\AM62X_TEye_A53_read_signed.appimage
    4. Once the signed image has been generated, you can call the UART bootloader to load the firmware with the appropriate COM port 
      1. python .\uart_bootloader.py -p COMx --cfg=.\sbl_prebuilt\am62x-sk-lp\eyetool_hsfs.cfg

    This worked on the EVM I borrowed, I believe this should also work for your setup as well.

    Sincerely,

    Lucas

  • 0 in reply to Lucas Bowe
    Prodigy 30 points

    Thank you Lurcas,

    Now the test is running.

    Do you have any application notes about tuning in the LPDDR4 RAM after getting the PDF report?

    Sincerely,

    Anders Joergensen 

  • 0 in reply to Anders Jørgensen
    TI__Expert 7255 points

    Greetings Anders,

    We do not. We typically recommend customers optimize their configuration based off simulation results, which has some guidance in the board design and layout guidelines app note: https://www.ti.com/lit/pdf/sprad06 

    Sincerely,

    Lucas