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.

PINMUX configuration after reset



Hello,

I am working with an OMAP l138 for signal processing. We have been developing our firmaware and hardware using the Experimenter Kit Dev Board. We have already made a prototype test that in general works fine.

However, I have recently realized that just after the boot, with the program in its begining, some PINMUX registers show different values from 0x00000000. As an example, PINMUX1 configures GPIO0[0] and GPIO0[6] as outputs what generates different troubles for the gobal system boot.

I have not seen this effect in the dev board and I am not sure where can it come from because it happens even before our software has started running.

Have you any idea about the origin of this problem and how I could solve it?.

Best regards.

  • Hi Marcos,

    PINMUX settings for the device can be changed using the ROM code by providing the PINMUX setting options from the AISGen tool that is used to generate the boot images. Could you ensure that the firmware used on the development boards and your custom board has the same PINMUX settings while generating the boot image.

    Regards,

    Rahul