Hello Team,
Could you help with our customer's question please.
They cant launch qmss on Linux.
Linux use keystone-uio.dtsi, where:
uio_qmss: qmss {
compatible = "ti,uio-module-drv";
mem = <0x02a00000 0x00100000
0x23a00000 0x00200000>;
};
In k2hk-uio.dtsi file this section is not redefined
In documentation: Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
qmss: qmss@2a40000 {
compatible = "ti,keystone-qmss";
dma-coherent;
This section is pulled through keystone-k2hk-netcp.dtsi
In documentation on QMSS module in Keystone 2 the base adress 0x02a00000 is changed to 0x02a40000
The question:
Is described above the reason of the following message(when the try to open QMSS transport):
TransportQmss Version : 0x02000001
Version String: Linux IPC Transports Revision: 2.0.0.01:Jan 23 2018:19:13:09
Process 1 : Initialized RM_Client0
Process 1 : Opening RM client socket /var/run/rm/rm_client0
fw_memMap: Failed to find fd to map 0x02a00000.
Process 1 : Creating TransportQmss instance
fw_memMap: Failed to find fd to map 0x02a00000.
TransportQmss_create : mpm_transport_open failed
name = "arm-qmss-generic", msg_size_bytes:4096, rm_service_h=0x830f68
ERROR Process 1 : Failed to create TransportQmss handle
Edit: Even after manual change of adresses the /dev/qmss still not appears.
The question 2:
When the /dev/qmss should appear? Which driver should be loaded?
“rmServer.out /usr/bin/device/k2h/global-resource-list.dtb /usr/bin/device/k2h/policy_dsp_arm.dtb” - was launched without errors.
Thank you in advance!
Ilya.