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.
we do have a problem with setting up our TMS320C6418 device using the HPI 16 boot process.
I'm trying to make it short so if you need additional information on how we setup up things, don't hesitate to ask.
The DSP HPI pins are all connected to GPIO pins on a MSP430F1481. HAS is tied high. HDS2 is tied high as well while HDS1 is low so that HCS alone should trigger HSTROBE. HCS is initially high so that HSTROBE is high too.
The MSP then sets all HPI inputs (data and controls) to their corresponding values and clears HCS. On the falling edge of HSTROBE the DSP should latch the control signals. We wait for HRDY low (which probably doesnt make much sense since the MSP is pretty slow compared to the DSP). Then we set HCS again so that the DSP latches the data on the rising edge of HSTROBE.
Is the procedure correct in this way?
Might it be a problem that the JTAG emulator (Signum JTAGjet) is connected to the DSP device? (the CC debugger is disconnected during the process though)
Fabion et Fronk
we tried two things later on yesterday:
First of all we read that HCS "serves as the enable input for HPI and must be low during access" (spru578c section 3.7). So now we use HDS1 for switching HSTROBE, while HCS stays low during the whole transfer of the two half-words. HDS2 is tied high.
We also tried switching GPIO[7:0] direction and output registers while JTAG was unconnected.
Both did not solve our problem.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Fabion et Fronk:
the problem has been solved!
It was a rather stupid programming bug. Sorry for any inconvinience.
For those who experience problems with HPI16, we want to say that the later described procedure does work.
So clear HCS to initiate data transfer and keep it low during the whole transfer of those two half-words. HDS2 (and HAS) is tied high, while HDS1 triggering HSTROBE (after HCS clear) for the control and data latches. Set HCS again after the whole word has been transferred.
Make sure to clear HD5 during the reset of the DSP to select HPI16 boot mode (input pins are high state on the dsp so it would choose HPI32 instead).
And also check HWOB in HPIC for the half-word order.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.