I’ve followed a lot of similar threads on this, like:
I know about the swi_setusbcomp.pl script, but I’m running in openWRT and I can’t get all the perl packages the script requires, so right now, I’m sending the commands manually using either perl’s pack, or PHP’s pack and I get the same results.
I have the 7455 in MBIM only with no com ports and I’m trying to get them back. I can do three out of the four steps, but I get an error with the actual 0x555c and I don’t know what it is. Here are the streams:
I don’t know what the 04 response means. I saw another example in another post where two bytes before the 5c 55 is 02 instead of 08, but I get the same 04 string as a response.
So, as far as I can tell looking online, 0x80000004 is a function error, and the last int is 0x00000003 which is MBIM_ERROR_LENGTH_MISMATCH ?
After the 5c 55 is 04 00, and there are 4 bytes after that, and I see a length of 10 for the QMI string, which seems right, and 11 for the length of the QMI over MBIM, which seems right, too?
Hi Peter,
the MBIM_ERROR_LENGTH_MISMATCH refers to the MBIM Message Length which is set to 61 (0x3d) but the complete MBIM message is 65 bytes as can be seen from tshark -x output:
DLT: 152, Payload: mbim.control (Mobile Broadband Interface Model)
Mobile Broadband Interface Model
Message Header
Message Type: COMMAND_MSG (0x00000003)
Message Length: 61
Transaction Id: 7
Fragment Header
Total Fragments: 1
Current Fragment: 0
Device Service Id: UUID_QMI (d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3)
CID: QMI (1)
Command Type: Set (1)
Information Buffer Length: 17
Information Buffer
Buffer: 0110000002030008005c55040001010006