>That's a great catch, nice work to figure that
out. I can't see yet why
>presence/absence of JTAGjet makes a difference. Is the "host-to-DSP
>interrupt" you mention associated with HPI? (If so it would be called
>DSPINT). Or is it associated with external interrupts (i.e. EINT4, EINT5,
>etc) ?
>
>-Jeff
>
It is DSPINT.
Gregor
Re: MCBSP UART not working after CSL upgrade ( sprc090 installation )
Started by ●November 6, 2006
Reply by ●November 6, 20062006-11-06
Gregor-
>>That's a great catch, nice work to figure that out. I can't see yet why
>>presence/absence of JTAGjet makes a difference. Is the "host-to-DSP
>>interrupt" you mention associated with HPI? (If so it would be called
>>DSPINT). Or is it associated with external interrupts (i.e. EINT4,
>> EINT5,
>>etc) ?
>>
>>-Jeff
>> It is DSPINT.
Ya that just sounds like an error in the CSL upgrade then. TI must have
made some assumption that another piece of TI software will come along and
allocate the first EDMA handle and use HPI.
-Jeff
>>That's a great catch, nice work to figure that out. I can't see yet why
>>presence/absence of JTAGjet makes a difference. Is the "host-to-DSP
>>interrupt" you mention associated with HPI? (If so it would be called
>>DSPINT). Or is it associated with external interrupts (i.e. EINT4,
>> EINT5,
>>etc) ?
>>
>>-Jeff
>> It is DSPINT.
Ya that just sounds like an error in the CSL upgrade then. TI must have
made some assumption that another piece of TI software will come along and
allocate the first EDMA handle and use HPI.
-Jeff
