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.

TMS320F28388D: A EMIF data pin can't be accessible from Docking Card | TMS320F28388D

Part Number: TMS320F28388D


Good morning colleagues,

I am using a TMS320F28388D with Docking Card. I have a question related to this thread: e2e.ti.com/.../tms320f28388d-emif-address-line-a11-and-data-line-d9-not-available-on-hsec180-docking-station
I want to use the data bus (not the address bus) to communicate via emif with an external memory (where the addressing is done with the address bus). I have the same problem that the D9 pin which is GPIO75 has no output on the Docking Card. I would like to know what solutions I can have about it because I need to use the 16 bus to communicate by EMIF. I hope you can help me with this, because I thought I could make use of all the functionalities...
Thank you very much,
Best regards
Pedro

  • Hello Pedro,

    I want to use the data bus (not the address bus) to communicate via emif with an external memory (where the addressing is done with the address bus).

    Sorry, I'm not sure what you mean by this. Are you not using the data bus as the data bus and the address bus as the address bus?

    I would like to know what solutions I can have about it because I need to use the 16 bus to communicate by EMIF.

    Have you already tried what Cody had stated in the linked post? Since this is a hardware limitation (i.e. the pin is not pinned out for the docking station), I believe this would be the only actual fix for the ControlCARD.

  • Sorry Omee, I wanted to say that I only want to use the data bus, not the address bus (I use data bus of 16 bits to write data and code in the memory (some bits are used to redirect and other bits to write im the memory)). 

    What you refer about Cody said IS this, isn't It "If you are really interested in 16b mode, you may be able to add a "blue wire" to bring GPIO 75 down from the Ethernet TX_D0 line to an unused pin in the edge connector. This would limit the speed of the interface, but could still work good for proving out your software."?? I find this solution a little bit bungle because in the future I plan to use the ethernet port. 

    The solution based on the Xbar is a solution I don't understand, if you could clarify It, I would appreciate It.

    Thank you in advance,

    Pedro 

  • What you refer about Cody said IS this, isn't It "If you are really interested in 16b mode, you may be able to add a "blue wire" to bring GPIO 75 down from the Ethernet TX_D0 line to an unused pin in the edge connector. This would limit the speed of the interface, but could still work good for proving out your software."?? I find this solution a little bit bungle because in the future I plan to use the ethernet port.

    I agree, this is more of a haphazard solution because of the limitation of the ControlCARD design, if you had the actual unit soldered onto your own PCB it would be a different situation (ControlCARDs are usually intended for quick verification of firmware and as such not every feature is available, although I agree that EMIF should have had this pin made available).

    The solution based on the Xbar is a solution I don't understand, if you could clarify It, I would appreciate It.

    Unfortunately I'm not very familiar with all the XBAR interconnections that can be used, I will let the XBAR expert answer whether there is a way to connect a GPIO so it can be read as the D9 EMIF input (GPIO 75).

  • Hi Pedro,

    I am not very familiar with EMIF, but this may be possible as long as the D9 pin is an output from the EMIF and not an input into the EMIF. To implement this you would need to configure an INPUTXBAR to read GPIO75, and then configure an OUTPUTXBAR to read this instance of INPUTXBAR and be routed out to another pin. If GPIO75 should be configured as an input, then there is no way to connect GPIO75 to a different GPIO and still use the EMIF functionality on that pin if you do not have access to GPIO75 on the board.

    Note that routing the signal through the XBARs will cause some delay, so it is possible that D9 will not be synchronized enough with the other data pins for the EMIF to function properly.

    Let me know if you have any further questions.

    Thank you,

    Luke

  • Thank you Luke. I think that I would use this pin as an input too because it would be necessary to read from the peripheral so I think that there is not a solution for this. 

    Have a nice day, thanks!