RM530NGLAAR05A01M4G_01.200.01.200Could you please provide a link to the kernel source code, or specifically the diagchar.h header file, that corresponds to this firmware version?
I am looking to identify ioctl commands to communicate with the modem
Dear @drNo_Whip
Sorry, I didn’t get your point.
It is standard firmware and don’t have other kernal source code.
If use linux, you can install driver and use AT port to communicate with modem.
My question is that, I’d like to communicate with the diagnostic protocol of the modem. I know that, as per the documentation, port /dev/ttyUSB0 is the diag port for the modem. I am able to successfully communicate with the modem via this port. However, as per qualcomms’ diag protocol, this port is suppose to support ioctl commands.
My testing proves that the option driver is associated with /dev/ttyUSB0 on the host and does not support any similar diagnostic ioctl calls. Since ioctl doesn’t work on /dev/ttyUSB0. Is there a different device node like /dev/diag that I should be using, or any other drivers? or are there proprietary AT commands?" If so, how do I enable this device node? or can you share the driver with me please?
In a nutshell, what is the officially supported mechanism to for ioctl commands for this firmware? Perhaps if I have access to the diagchar.h (or libdiag.so which is on every qualcom’s chipsets) used to build the firmware, I find this out myself.
Current chipset on my device is the X62
Let me know if you I can clarify anything for you.
Seems that you are using the standard firmware.
For standard firmware, Quectel and even Qualcomm only provide the ttyUSB port for customer.
For RMNET network interface, it would provide the /dev/cdc-wdm0 for QMI message. If you are familar with the Qualcomm QMI, you can try something like libqmi.
There is no any customerized ioctl API for the customer to access the modem.