I was trying to get statrted with hpi data transfer on a 6711 dsk. I
adapted the dsk6xldr project and the cnfdsp code in the examples. The
dsp writes some magic numbers in memory that is recognized to get the
load time dsp address, and then queries the array of 0x400 values (or
0x200). EMIF initialization set to true made the internal ram work
fine, but the external ram would give most, but not all, the values
the dsp target had written into them. Only about 3 or 4 values per
0x100 values are wrong and usually come in groups of 3.
(Please advise if/how I should post code.)
Reply by Mike Dunn●July 29, 20042004-07-29
Hello Malcolm[?],
There seems to be a bug in the TI/HPI write code - please see the archives
of this list. there have been several discussions on the topic.
mikedunn
malcolmwindham <m...@yahoo.com>
wrote:
I was trying to get statrted with hpi data transfer
on a 6711 dsk. I adapted the dsk6xldr project and the cnfdsp code in the
examples. The dsp writes some magic numbers in memory that is recognized
to get the load time dsp address, and then queries the array of 0x400
values (or 0x200). EMIF initialization set to true made the internal ram
work fine, but the external ram would give most, but not all, the values
the dsp target had written into them. Only about 3 or 4 values per 0x100 values are wrong and usually come in groups of 3.
(Please
advise if/how I should post code.) _____________________________________ Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you want
your answer to be distributed to the entire
group.
_____________________________________ About this
discussion group:
