Transliterated backwards
Jan. 9th, 2011 12:04 amI have been struggling with writing software to control something over an I2C bus. Because it is more than slightly complex I captured the bus transactions using demo software running on a PC, to identify some of the settings needed.
I realise that I had been searching a bus capture made using demo software incorrectly. Though one part of the programming manual tells me that a certain set property command starts with a two byte command and is followed by 8 arguments, I naturally assumed that SET_PROPERTY_FOO: 0x0602 would mean that the bytes 0x06 and 0x02 would be sent in order before the arguments.
NO!
It is in the order 0x02 then 0x06, then followed by the arguments. It must be that way round, because the first line of the example on page 243 or whatever is the address, so it must be starting from the top, not the bottom. Because it is transliterated from the original Japanese, I should have guessed that 0x0602 actually means 0x0206. Of course! I should have instinctively known.
It is beginning to make sense, but I still think that power electronics, or even RF, makes much more sense. [sigh]
I realise that I had been searching a bus capture made using demo software incorrectly. Though one part of the programming manual tells me that a certain set property command starts with a two byte command and is followed by 8 arguments, I naturally assumed that SET_PROPERTY_FOO: 0x0602 would mean that the bytes 0x06 and 0x02 would be sent in order before the arguments.
NO!
It is in the order 0x02 then 0x06, then followed by the arguments. It must be that way round, because the first line of the example on page 243 or whatever is the address, so it must be starting from the top, not the bottom. Because it is transliterated from the original Japanese, I should have guessed that 0x0602 actually means 0x0206. Of course! I should have instinctively known.
It is beginning to make sense, but I still think that power electronics, or even RF, makes much more sense. [sigh]