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

RTOS/AM5728: RTOS/AM5728:

veronica klotz
Prodigy 40 points
Part Number: AM5728
Other Parts Discussed in Thread: BEAGLEBOARD-X15,

Tool/software: TI-RTOS

We use the BeagleBoard-X15 to train us into the multiprocessor system from AM5728.

The A15-0 should communicate with the DSP1 via IPC.

The development environment:

For debugging we use XDS200.

For the A15-0 we use XUbuntu with the ti-processor-sdk-linux-am57xx-evm-05.00.00.15.

For RTOS on the DSP1 we use Windows 10 and the Code Composer Studio.

To load the RTOS binary file on the DSP1, we stop the UBoot and then we followed your instructions.

We had no problems with this method.

Now we started to develop with our own board.

On the Linux side, we have no problems.

But if we stop the UBoot to load the RTOS code on the DSP we always get an error message that the GEL files can not be loaded.

Only if we remove the SD card it is possible to load the code into the DSP1.

We compared the configuration files from the BeagleBoard-X15 and the new board, but we did not notice any differences.

What reasons can it have that the GEL file can not be loaded? 

Thanks for your efforts and kind regards,

Veronica Klotz

  • 0
    TI__Guru 50170 points
    Hi, Veronica,

    Stopping u-boot, I assume you hit the keyboard to stop the booting and at the u-boot prompt. The possible reason I can think of is the DSP may not be powered up, but it seems that you were able to connect to DSP, but failed to load the GEL file.

    I'll have the DSP expert to take a look what could be the problem.

    Rex
  • 0
    TI__Mastermind 27355 points
    Hello Veronica,

    Loading the DSP image should be done via remoteproc. When the DSP image is loaded from /lib/firmware, the Linux kernel remoteProc framework will parse the system resources defined in resource table that is linked into DSP image, allocate rpmsg vring buffers and trace buffer, and configure the MMU of DSP. If you load the DSP image with CCS JTAG connection, the step will be skipped and you should observe different results when trying to establish the communication between host and DSP. You may check the MMU config discrepancy with the two approaches by looking into the TLB page table: cat /sys/kernel/debug/omap_iommu/<iommu_name>/pagetable.

    After the DSP image is loaded from /lib/firmware, you can connect to the core from CCS without running any GEL files, and then load only the image symbols to examine the code and debug.

    Regards,
    Sahin