Activity
From 11/11/2011 to 12/10/2011
11/15/2011
- ML 03:30 PM Software Development: RE: OMAP I2C
- Yes, it works (thanks):
- JP 03:24 PM Software Development: RE: OMAP I2C
- Mark,
I probably should have used O_RDWR instead of O_RDONLY. I am surprised it worked with just O_RDONLY.
The SENDRECV is important, at least for my device. I am reading a device register and the protocol is that I need to send th... - ML 03:17 PM Software Development: RE: OMAP I2C
- Interesting. We were using Qnx's demo which uses DCMD_I2C_RECV rather than DCMD_I2C_SENDRECV so that was part of the solution.
It is also calling open with O_RDWR rather than O_RDONLY - not sure if that is a problem.
Also the call t... - JP 01:27 PM Software Development: RE: OMAP I2C
- I am attaching a test program that was used on a board to read the factory config information using i2c0.
The output of the i2c_get program is:
11/14/2011
- JP 05:13 PM Software Development: RE: OMAP I2C
- Can you try to get the sample program that the qnx engineer used?
Thanks.
- ML 09:47 AM Software Development: RE: OMAP I2C
- An engineer from QNX hooked a scope to I2C0 lines on their EVM board and sent the sendrecv command. They were able to get a signal on the lines, proving that their driver works with the utilities. They said this indicated that the BSP wa...
11/11/2011
- JP 03:04 PM Software Development: RE: OMAP I2C
- IFor what it is worth, it should be noted that the i2c accesses in the startup code and in the i2c_get utility are done without interrupts. The i2c resource manager is probably using interrupts. It is possible that something needs to be ...