- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software: Linux
Hi,
So I have a problem being able to load compiled TI-RTOS DSP Firmware from my Linux.
This DSP firmware is a modified TI-RTOS example, it's the USB Audio Example that is compiled for the OMAP-L138.
I have a added a custom resource table to the project and tried to modify the .bld file and the RTSC configuration file using some settings from the MessageQSingle example but the end results in the Linux kernel locking up completely after loading the firmware and the firmware doesn't actually work when loaded this way.
The Firmware works when loaded through the CCS Debug directly into the C6748 inside the chip through a JTAG Debugger.
root@omapl138-lcdk:~/Projects# cd /lib/firmware/ root@omapl138-lcdk:/lib/firmware# ls ipc rproc-dsp-fw root@omapl138-lcdk:/lib/firmware# unlink rproc-dsp-fw root@omapl138-lcdk:/lib/firmware# ln -s ipc/ti_platforms_evmOMAPL138_DSP/omapl138_usb_audio_dsp.out rproc-dsp-fw root@omapl138-lcdk:/lib/firmware# ls -l drwxr-xr-x 3 root root 4096 Jun 4 2018 ipc lrwxrwxrwx 1 root root 59 Mar 26 15:31 rproc-dsp-fw -> ipc/ti_platforms_evmOMAPL138_DSP/omapl138_usb_audio_dsp.out root@omapl138-lcdk:/lib/firmware# cd /sys/bus/platform/drivers/davinci-rproc/ root@omapl138-lcdk:/sys/bus/platform/drivers/davinci-rproc# echo davinci-rproc.0> unbind remoteproc remoteproc0: releasing dsp root@omapl138-lcdk:/sys/bus/platform/drivers/davinci-rproc# echo davinci-rproc.0> bind davinci-rproc davinci-rproc.0: assigned reserved memory node dsp_cma@c3000000 remoteproc remoteproc0: dsp is available root@omapl138-lcdk:/sys/bus/platform/drivers/davinci-rproc# remoteproc remoteproc0: powering up dsp remoteproc remoteproc0: Booting fw image rproc-dsp-fw, size 5462468 virtio_rpmsg_bus virtio0: rpmsg host is online remoteproc remoteproc0: registered virtio0 (type 7) remoteproc remoteproc0: remote processor dsp is now up
This is the set of commands executes to copy the built .out file I compiled in the CCS, linking it to the system link file and then using remoteproc to execute it.
Following this, the Linux kernel locks up and the LCDK Boards has to be restarted. The Linux kernel is running from an SD Card.
In order to get the IPC source table to work, I had to modify the RTSC board settings file for the evmOMAPL138.
I had to modify the DDR to be 0xC100000 since IPC uses 0xC0000000 to 0xC1000000.
I attached the configuration, build and the project files.
I want to just be able to load the firmware via the remoteproc and the later attach Shared Memory support to be able utilize the 128 KB of ARM/DSP shared
memory to share data buffers.
Hello Dmitriy,
Just an FYI, you can change the memory configuration directly from the config.bld instead of changing the RTSC platform. All you have to do is append :dsp to your platform in project properties and it will automatically pick up the platform table specified in config.bld.
The nice thing about the config.bld is that you can make memory configuration changes directly from the application level. Your method works too, I just wanted to let you know about this option.
Now, to get this example running on the DSP when the ARM is running Linux, you will need to make sure the cores are not trying to use and initialize the same peripherals. You can look at the device tree source (DTS) files to see what is being used by the ARM core. For OMAP-L138, da850.dtsi contains the SoC-level definitions, and da850-lcdk.dts contains the board level definitions (da850 and omapl138 are equivalent devices). These files are located under ti-processor-sdk-linux/board-support/linux/arch/arm/boot/dts.
For starters, by looking at mcasp_cfg.h on the DSP side, and the DTS files, I can see that both cores are trying to use MCASP0, EDMA0, and I2C0.
You have a few options:
For example, to disable UART3 and prevent the kernel from putting it to sleep, you would add the following to the device tree:
&uart3 {
status = "disabled";
ti,no-idle;
};3. Change the DSP cfg or device tree so that the cores are using different instances of each peripheral, i.e., ARM uses MCASP0 and DSP uses MCASP1.
The wiki linked below explains how to add IPC to an existing application for AM572x. It's for a different device, but the process is the same as what you are doing here.
If you have any questions please let me know.
Hi Sahin, I was able to compile and load the the Firmware into the DSP from the ARM, however it doesn't work, I think because McASP isn't initialized because I commented out "board_init" function inside this function.
void configureAudio(void)
{
Board_STATUS stat = BOARD_SOK;
Board_initCfg arg = BOARD_INIT_PINMUX_CONFIG | BOARD_INIT_UART_STDIO;
//stat = Board_init(arg);
return;
}
I followed instructions in this link, but I don't think McASP nor USB is starting because of the board_init function. I have disabled USB/MCASP/EDMA/I2C inside the device tree and the Linux Kernel Menuconfig.
