• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 245 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

shell bug

DavidVescovi
Genius 5470 points

I noticed in the A8_1.00 release the omap shell extension the R/W twl register function does not work.

I am opening in a command window in the UI and doing, for example, "do intwl 4B 0".

This throws an exception. It seems the root cause has to do with the twl command calling via some I2C kernelIoctrl that are not available in user context.

I believe the correct way for the twl command to work is to call via the I2C1 proxy. Is this a correct assumption?

I guess another way would to be to add the offending KernelIoctrl's to the oemKernelIoctrl table and make sure everything is marshalled correctly, but seems like a much harder path.

I guess I could acheive the same results by using the ini2c 1 xx yy command as this command does seem to work (even though the text label on both the i2c R/W command is also incorrect) and read the TWL register this way. Does this make sense? I do not follow how the TWL register addressing would be mapped if using this technique though?

  • 0
    TI__Expert 5320 points

    Hi David

    yes, there is an exception when accessing intwl and outtwl commands due to IOCTL not available to user space processes/modules. In the next release, these commands will be deprecated and removed. One should use the ini2c commands to access the twl regs. The first argument should be 1 (as you have figured it out already). The address and subadress argument to ini2c should remain the same as that to intwl command. The command help for in/out i2c commands will be updated.

    -Madhvi

  • 0 in reply to Madhvi
    TI__Genius 9185 points

    This issue is being tracked as SDOCM00072602. 

    (If the link does not work please flush your browser cache and try again).