• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1064 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.

Problem with pinmux settings of a custom board in board project.

Jacek Jaworski
Expert 1325 points
Part Number: TMDSIDK437X
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Starterware

Hi,

I use sysbios ind sdk 2.1.1.2 with ccs 6.1.2. I wrote some code on idkam437x which I would like to migrate to a custom board. The most ambiguous thing for me is the pinmux modification in 'board' project in sysbios starterware. Basically, I have a few questions:

1. I copied the pinmux configuration derived from pinmux cloud tool to the 'custom' pinmux configuration - is this a good choice? Maybe I should organize a new configuration and refer it to the UNKNOWN board? I do not really know if my new configuration is read from all the pinmux options when using PINMUXModuleConfig() function in my project? I see that one of the pinmux options is chosen based on the information read from the EEPROM memory - from my custom board obviously no information will be read so which pinmux option (and at which project stage) will be chosen?

2. There are several CHIPDB_MOD IDs generated from pinmux cloud tool that do not work properly for my project, e.g.:

CHIPDB_MOD_ID_ARM 

CHIPDB_MOD_ID_ADC

CHIPDB_MOD_ID_OSC

CHIPDB_MOD_ID_GLUE

CHIPDB_MOD_ID_SPI

The problem is they are used in the final pin configuration for pinmuxBoardCfg_t structure, however they do not exist in chipdb_defs.h file. I suppose there is some mismatch between pinmux tool and sysbios sdk 2.1.1.2 and 2.1.2.2. What should I do with that - try to modify it by hand?

Thanks!

JJ

  • 0
    TI__Guru** 116170 points
    JJ,

    We don`t have an example of modifying the pinmux setup for the AM437x IDK but we have a simple example using AM335x that you can use as reference.
    www.ti.com/.../sprac32.pdf ( This demonstrates use of pinmux tools to modfy default UART on AM335x based Beagle bone black)

    If your custom board is based on AM437x IDK then you can replace the existing configuration with the new configuration that you have obtained from the pinmux tools. Ideal way to start would be to import the AM437x IDK configuration into the tool and then modify just the interfaces that are configured differently on your board and then replace the starterware files with the generated configuration.

    The latest pinmux tools is aligned to work with the PDK packages that are used in the Processor SDK RTOS. Unfortunately this means that there may be some mismatches with the industrial SDK which you will need to hand modify manually.

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    Expert 1325 points

    Hi Rahul,

    Thanks for your answer.

    But if I download modified IDKAM437X pinmux configuration into my custom board, no data will be read from its EEPROM during initialization and the board will be detected as 'unknown' - so the idkam437x pinmux configuration will not be used, am I right?

    I supposed some changes in the pinmux cloud tool related to pdk, however even in the newest version of PDK there are no such Chipdb IDs:

    CHIPDB_MOD_ID_ARM

    CHIPDB_MOD_ID_OSC

    CHIPDB_MOD_ID_ADC (as in sysbios sdk there are only CHIPDB_MOD_ID_ADC0 and CHIPDB_MOD_ID_ADC1 )

    so even when using the newest pdk the problem would exist - I was prepared for changing some details manually but I see no reference even in the newest sysbios/pdk sdk. 

    Regards,

    JJ