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