• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 272 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:

Linux/AM5749:How to add sata ssd drive.

Linux/AM5749:Failed to open EVE message queue

Oleg Solovev
Expert 1985 points
Other Parts Discussed in Thread: AM5749

Hello support!!!

I use ti-processor-sdk-linux-am57xx-evm-06.03.00.106 on am5749(custom board).

How you can see here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/946966/linux-am5749-how-to-add-sata-ssd-drive/3512990#3512990

I realized load U-boot from  S25FL256S (qspi1) and load the kernel and device tree from SATA. Everything work is fine except Opencl examples (located here: /usr/share/ti/examples/opencl/) and everything what use Opencl.

I have errors like this one: TIOCL FATAL: Failed to open EVE message queue

The reason is very simple. I 've wrote MLO and u-boot.img on S25FL256S but I forgot about this one: dra7-ipu1-fw.xem4.

The qustion is:

1.How to write dra7-ipu1-fw.xem4 on S25FL256S for normal work Opecl through U-boot.

2.Where exactly it is should be located. I mean adress or maybe it is doesn't matter. 

3.dra7-ipu1-fw.xem4 used for loading some frimeware on EVE cores?

4.Why in system we should have two dra7-ipu1-fw.xem4 files. First on boot part another one located lib/firmware  is it correct?

BR,

Oleg

  • 0
    TI__Guru**** 162490 points

    Hi Oleg,

    Can you share the complete boot logs? From MLO to Kernel?

    I believe u-boot.img & MLO are flashed to QSPI. How about the kernel/dtb and file system where are they present?

    On 6.03 the SPL loads the dra7-ipu1-fw.xem4 firmware. That is only supported from SD boot.
    Also that is a firmware for IPU and not EVE.

    The DSP_EVE firmware are loaded by kernel from the filesystem:

    [ 13.403009] remoteproc remoteproc2: powering up 40800000.dsp
    [ 13.408703] remoteproc remoteproc2: Booting fw image dra7-dsp1-fw.xe66, size 20482288
    [ 13.416805] omap-iommu 40d01000.mmu: 40d01000.mmu: version 3.0
    [ 13.422703] omap-iommu 40d02000.mmu: 40d02000.mmu: version 3.0
    [ 13.439454] virtio_rpmsg_bus virtio2: rpmsg host is online
    [ 13.446525] remoteproc remoteproc2: registered virtio2 (type 7)
    [ 13.453900] remoteproc remoteproc2: remote processor 40800000.dsp is now up
    [ 13.463037] virtio_rpmsg_bus virtio2: creating channel rpmsg-proto addr 0x3d
    [ 13.471539] omap-hdmi-audio omap-hdmi-audio.0.auto: snd-soc-dummy-dai <-> 58040000.encoder mapping ok
    [ 13.482079] omap-hdmi-audio omap-hdmi-audio.0.auto: ASoC: no DMI vendor name!
    [ 13.862882] davinci_mdio 4b2b2400.mdio: davinci mdio revision 1.6, bus freq 1000000
    [ 13.877694] libphy: 4b2b2400.mdio: probed
    [ 13.905052] davinci_mdio 4b2b2400.mdio: phy[0]: device 4b2b2400.mdio:00, driver TI TLK10X 10/100 Mbps PHY
    [ 13.920006] davinci_mdio 4b2b2400.mdio: phy[1]: device 4b2b2400.mdio:01, driver TI TLK10X 10/100 Mbps PHY
    [ 13.947688] remoteproc remoteproc3: powering up 41000000.dsp
    [ 13.953514] remoteproc remoteproc3: Booting fw image dra7-dsp2-fw.xe66, size 20482288
    [ 13.961508] omap-iommu 41501000.mmu: 41501000.mmu: version 3.0
    [ 13.967460] omap-iommu 41502000.mmu: 41502000.mmu: version 3.0
    [ 13.979585] PVR_K: UM DDK-(4948957) and KM DDK-(4948957) match. [ OK ]
    [ 14.011656] remoteproc remoteproc4: 4b234000.pru is available
    [ 14.020413] virtio_rpmsg_bus virtio3: rpmsg host is online
    [ 14.027588] remoteproc remoteproc3: registered virtio3 (type 7)
    [ 14.027694] pru-rproc 4b234000.pru: PRU rproc node pru@4b234000 probed successfully
    [ 14.042825] remoteproc remoteproc3: remote processor 41000000.dsp is now up

    Pasting boot log from default 6.03 SDK on AM574x-idk.

    So i believe what you are looking for is the remoteproc2 & remoteproc3 which are both DSPs.

    cat /sys/class/remoteproc/remoteproc2/name
    40800000.dsp
    root@am57xx-evm:~# cat /sys/class/remoteproc/remoteproc2/firmware
    dra7-dsp1-fw.xe66
    root@am57xx-evm:~# ls -l /lib/firmware/dra7-dsp1-fw.xe66
    lrwxrwxrwx 1 root root 46 Apr 20 2020 /lib/firmware/dra7-dsp1-fw.xe66 -> /lib/firmware/dra7-dsp1-fw.xe66.opencl-monitor

    This is loaded by kernel from the file system.


    Oleg Solovev said:
    3.dra7-ipu1-fw.xem4 used for loading some frimeware on EVE cores?

    No it is for IPU which is M4.

    Oleg Solovev said:
    4.Why in system we should have two dra7-ipu1-fw.xem4 files. First on boot part another one located lib/firmware  is it correct?

    This is again irrelevant for EVE.

    Best Regards,
    Keerthy