• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 97 subscribers
  • Views 1238 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.

TMDSICE3359: Flashing PRP image to SPI flash

Dawid Balcerzak
Expert 1365 points

Part Number: TMDSICE3359
Other Parts Discussed in Thread: SYSBIOS

Hello.

By following this:

I was trying to flash PRP example to TMDSICE3359 EVM board. I prepared _ti.bin files, flashed bootloader (bootloader_boot_mcspi_a8host_release_ti.bin) and next my application. Next I reset system and here it is what I see on terminal:

but nothing more happened. Did I do something wrong?

BR,
Dawid.

  • 0
    TI__Guru**** 393215 points
    The RTOS team have been notified. They will respond here.
  • 0 in reply to Biser Gatchev-XID
    Expert 1365 points

    I tried flashing with both bootloaders. I mean bootloader_boot_mcspi_a8host_release_ti.bin and bootloader_boot_mcspi_a8host_debug_ti.bin.  Result still the same. But in instruction from the link in my first post there is a line: To flash application binary image <app_name>_a8host_ti.bin, provide 0x20000.  But my files doesn't have a8host part in name. I just followint instructions and I created binary by TOOLCHAIN_PATH_<A8/A9>/bin/arm-none-eabi-objcopy -O binary <application>.out <application>.bin and tiimage.exe <Image Load Address> NONE <application>.bin <application>_ti.bin next. Is there something I could missed?

  • 0 in reply to Dawid Balcerzak
    TI__Guru** 116950 points
    Dawid,

    In addition to the information that you have provided here, can you also specify the Image Load Address that you used. when creating the app.
    the reason that I ask that is that it appears your application is being loaded to location 0x0 which I am not sure is correct. The application runs in DDR memory, so I would have expected the dst address to be 0x8XXX_XXXX format and not 0x0.

    For most of the SDK examples, this is the command that we run :
    %PDK_PATH%/ti/starterware/tools/ti_image/tiimage.exe 0x80000000 NONE %APP_NAME%.bin app

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    Expert 1365 points

    Rahul,

    thank you for your reply.

    You were right. My destination address was wrong. I didn't know correct address. I prepared files again using correct address: 0x80000000. In command window I typed:

    tiimage.exe 0x80000000 NONE prp_app_AM335x_arm.bin prp_app_AM335x_arm_ti.bin

    After long process of flashing here it is my log from terminal:

    And nothing more happens. It looks like I made another mistake. What should I check next?

    BR,

    Dawid.

  • 0 in reply to Dawid Balcerzak
    Expert 1365 points

    Rahul,

    false alert. It hungs because I didn't close debugger session in CCS. After closing debugger session and restarting ICE v2 board it fired correctly. Here my log is:

    Thank you very much Rahul for your help. I appreciate it very much.

    Thanks again,

    Dawid.

  • 0 in reply to Dawid Balcerzak
    Expert 1365 points
    BTW, I have one more little question - should I load TMDXICE3359_v2_1A.gel when I use PRU-ICSS like in instructions for SYSBIOS IND SDK? In instructions from processors.wiki.ti.com/.../AM437x there is no information about it.
  • 0 in reply to Dawid Balcerzak
    TI__Guru** 116950 points
    Dawid,

    GEL and bootloaders are two conflicting ways of setting up the SOC initialization and loading the app. GEL setup is used only when you are debugging and prototyping your application when loading the .out on the ARM core using a JTAG emulator. Bootloader is used in production environment, when the application is loaded and run from a flash or host interface. When you are in production environment and load the application from boot media, you should typically not use the GEL as it will over ride the clock and DDR settings which can cause the application running on the SOC to crash.

    Regards,
    Rahul