I have not seen a more recent question/answer on this topic.
Is it possible to do a multiple read transaction using "board.ReadI2C()" in the ALP scripting tab? It is not possible to fully troubleshoot I2C devices on the remote I2C bus unless one can read back more than 8 bits in one transaction.
Thank you,
Mike
Michael,
Make sure you have installed the ALP framework v1.57.0010 from the web and also the latest ALP-PROFILE-UPDATE (v10). Please check you have the latest as below
Thanks,
Vishy
I am not sure if you can see the picture above, it seems to be of a much lower quality than I captured.
board.rc is reporting "1". I have my PC plugged into the eval board with a 926 (local device) and the link is to a 921 (remote device). I have set up SlaveID and Slave Alias ID for the two other devices on the remote side I2C bus. Local device address is 0x58. Remote device address is 0x18. The two other devices on the remote bus are addresses 0x46 and 0x52. I have set the SlaveID and the Slave Alias to be the same value for each device for test purposes.
I am looking at the waveforms on the I2C remote bus with an oscilloscope. When I run single byte commands, the output on the bus matches the command. I can communicate with the two remote devices - I can write to 0x46 or 0x52 with a register value and a single data byte, and I see an ACK on the bus from these devices.
When I run a two byte command, "board.WriteI2C(0x52,0x01,[0x1A,0x05]) I only see the device address 0x52, the register value 0x01 and the first data byte 0x1A, then STOP on the scope.
