MOST ctrl by os81050 in F10 BMW's

Hello everyone, I want to replace my BMW dashboard(F10), and I encountered a problem that the fiber control commands/responses need to be parsed. I grabbed some data from the fiber, using the OS81050 chip, through I2C. I got some data as follows:

  • 0x00 0x15 0x05 0x04 0x01 0x00 0xE0 0x00 0x51 0x5C 0x00 0x0B 0x00 0x00 0x05 0x0D 0x1C 0x38 0x01 0x0F 0x01 0x07 0xE6
  • 0x00 0x0F 0x06 0x04 0x00 0x01 0x00 0x02 0x00 0xA0 0x1C 0x00 0x04 0x01 0x00 0xCA 0x00
  • 0x00 0x0E 0x05 0x04 0x01 0x00 0xE0 0x00 0x00 0x1F 0x00 0x04 0x20 0x10 0x02 0x00

decode frames following https://moderndaymods.com/how-most-bus-control-messages-work/, it looks like not match. Is there any step in the analysis that is incorrect?

frame0:
0x00 0x15 0x05 0x04 0x01 0x00 0xE0 0x00 0x51 0x5C 0x00 0x0B 0x00 0x00 0x05 0x0D 0x1C 0x38 0x01 0x0F 0x01 0x07 0xE6

  • 0x00 0x15 : frame length
  • 0x05 0x04 0x01: what is it?
  • 0x00 0xe0 :device id ?
  • 0x00 :fblock id
  • 0x51 :inst
  • 0x5C 0x00 : op_type 0x0, fkt id: 0x5c0
  • 0x0B :tel_id&tel_len, data length is 0x0B , tel id :0x0
    • [00 00 05 0D 1C 38 01 0F 01 07 E6] : data

frame1:
0x00 0x0F 0x06 0x04 0x00 0x01 0x00 0x02 0x00 0xA0 0x1C 0x00 0x04 0x01 0x00 0xCA 0x00

  • 00 0F : frame length
  • 0x06 0x04 0x00 0x01 : what is it?
  • 0x00 0x02 :device id ?
  • 0x00 :fblock id
  • 0xA0 :inst
  • 0x1C 0x00 : op_type 0x0, fkt id: 0x1c0
  • 04 :tel_id&tel_len, data length is 0x04 , tel id :0x0
    • [0x01 0x00 0xCA 0x00] : data

frame2:
0x00 0x0E 0x05 0x04 0x01 0x00 0xE0 0x00 0x00 0x1F 0x00 0x04 0x20 0x10 0x02 0x00

  • 00 0E : frame length
  • 0x05 0x04 0x01 : what is it?
  • 0x00 0xE0 : device id ?
  • 0x00 : fblock id
  • 0x00 : inst
  • 0x1F 0x00 : op_type 0x0, fkt id: 0x1F0
  • 04 :tel_id&tel_len, data length is 0x04 , tel id :0x0
    • [0x20 0x10 0x02 0x00] : data

It’s hard to tell from this what relates to the OS8104 communications. The OS81050 is an entirely different chip, and is an INIC type. I can’t seem to find much in the way of data sheets so it’s kind of hard to point you in the right direction. I can say that 0x00 is not a valid fblock or instanceID