Failed opening I2C device from Application

Luan Le

Other Parts Discussed in Thread: OMAP3530

Hi everyone,

I have a OMAP3530 custom board with WinCE 6.0 / BSP ARM_A8_1_00. I successfully tested the I2C using a subproject. However, I could not open I2C from my application with the SDK that I created from my OS Design; CreateFile(_T("I2C2:"), GENERIC_READ|GENERIC_WRITE, 0, NULL, OPEN_EXISTING, 0, NULL) return -1.

Opening COM or SPI works fine. Opening "I2C1:" also failed.

Would you please give me some tip on how debug this issue?

Thanks,

Luan

over 14 years ago

0 Madhvi over 14 years ago

TI__Expert 5320 points

After boot-up, can you check the registry if the I2CProxy drivers are getting loaded or not?

0 Luan Le over 14 years ago in reply to Madhvi

Expert 2280 points

Hi Madhvi,

My device boots from NAND. Can you show me how to check the registry to see if the I2CProxy drivers are getting loaded or not?

Thanks,

Luan

0 Madhvi over 14 years ago in reply to Luan Le

TI__Expert 5320 points

One way would be to use Remote Tools (registry editor) using TCP/IP transport and manual startup server.

http://msdn.microsoft.com/en-us/library/ee481438.aspx

0 Adeneo Embedded support team over 14 years ago in reply to Madhvi

Mastermind 9310 points

The I2C proxy driver should be automatically loaded if the "TI Shell extensions" item is selected in your OsDesign catalog (BSP_SHELL_EXTENSIONS_DO_CMD). If you have an active KITL connecttion to your booted board, try typing "gi mod" under the target control windows to display a list of loaded modules. You should have "i2cproxy.dll" listed in order to have the I2C proxy driver available to your application.

0 Luan Le over 14 years ago in reply to Adeneo Embedded support team

Expert 2280 points

Thanks Adeneo Embedded support team. I have found out that I did not have the "TI Shell extensions" item in my OsDesign catalog selected. I select it and it now works.

Thanks,

Luan

Processors

Processors forum

Failed opening I2C device from Application