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.

TMS320F280049C: Driving unavailable GPIO pins

Part Number: TMS320F280049C

Hello,

We have developed an application on an F280049C processor and are using some GPIO pins to forward some debugging information. But the final application uses a 64-pin version of this chip, so these used debug pins are not available outside. But is it bad if these IO pins are still being used by the program and switch the outputs or do we have to remove these output pins in the final software ?

  • Jan,

    I think there is little to no risk here, since the IO signal is not brought out to a pin, it is just a floating node inside the package.  Since there is no load attached the current draw by still using these pins will be minimal(less than on the implementation that has these pinned out) and any noise effects should be minimal as well.

    You could leave the mux selection as input(this is the default) and any action writing to the pins will have no effect but will just use some CPU cycles.

    If you wanted maximum flexibility you look at the PARTIDL register in the code, bits 8-10 give the pin count of the device, and you could deterministically use certain GPIOs.

    Below is from page 313 of the TRM

    Best,

    Matthew