Forums

Problem with Code composer studio connecting with big endian.

Started by Benne January 19, 2009
Hi.
I have a board with a TMS320C6727.
My other equipment is JTAGjet from Signum and Code composer studio
3.3.

I can connect with the board easily. But sometimes it connects with
little endian, and sometimes big endian.
Both the DSP and the JTAG supports both. However, my piece of firmware
which I need to install is only little endian.

So sometimes I can't download this piece of firmware since it isn't
the same endianness...

Does anyone have a good idea on how I can make CCS always connect as
Little endian? It doesn't seem to be possible though...

/Best regards, Ben
On 19 Jan, 13:32, Benne <ben.wieg...@gmail.com> wrote:
> Hi. > I have a board with a TMS320C6727. > My other equipment is JTAGjet from Signum and Code composer studio > 3.3. > > I can connect with the board easily. But sometimes it connects with > little endian, and sometimes big endian. > Both the DSP and the JTAG supports both. However, my piece of firmware > which I need to install is only little endian. > > So sometimes I can't download this piece of firmware since it isn't > the same endianness... > > Does anyone have a good idea on how I can make CCS always connect as > Little endian? It doesn't seem to be possible though...
At the risk of exposing my inexperience with HW: Is there a HW switch for this? The manufacturer of the DSP chip can not possibly know if the chip will be used in a little endian or big endian environment. The user knows, but is unlikely to change his opinion once the decision has been made. So configuring this in SW is waste of run-time. All in all, a HW switch seems to be a very likely way to control this. Rune
> > At the risk of exposing my inexperience with HW: > > Is there a HW switch for this? The manufacturer of the DSP chip > can not possibly know if the chip will be used in a little endian > or big endian environment. The user knows, but is unlikely to > change his opinion once the decision has been made. So configuring > this in SW is waste of run-time. > > All in all, a HW switch seems to be a very likely way > to control this.
As far as I can see there is no switch or jumper on it. But i will try to contact the manufacturer. But it is really odd I think that it sometimes connects as little endian and sometimes not. It's as if it were random...
Benne <ben.wiegert@gmail.com> writes:

>> >> At the risk of exposing my inexperience with HW: >> >> Is there a HW switch for this? The manufacturer of the DSP chip >> can not possibly know if the chip will be used in a little endian >> or big endian environment. The user knows, but is unlikely to >> change his opinion once the decision has been made. So configuring >> this in SW is waste of run-time. >> >> All in all, a HW switch seems to be a very likely way >> to control this. > > As far as I can see there is no switch or jumper on it. But i will > try to contact the manufacturer. > But it is really odd I think that it sometimes connects as little > endian and sometimes not. It's as if it were random...
It seems I remember some GPIO pins that configured this option on power-up on the 6x family. Perhaps leaving the pin(s) open produces the behavior you're observing? -- % Randy Yates % "Remember the good old 1980's, when %% Fuquay-Varina, NC % things were so uncomplicated?" %%% 919-577-9882 % 'Ticket To The Moon' %%%% <yates@ieee.org> % *Time*, Electric Light Orchestra http://www.digitalsignallabs.com
I checked the schematics, and the GPIO are set. I don't remember if
they were set low or high now since I am at home sick. But I passed by
my office the other day and checked the schematics in a haste.

I am running out of ideas now... But also, maybe being sick reduces
the amounts of ideas I get ;)
It is not really random I noticed. Maybe like 90% of the times it
connects as big endian.


Anyway, I am thinking about getting another JTAG-emulator. The XDS510
instead. That is the one used at the other factory I found out.
But I am pretty sure that my current JTAG-emulator has exactly the
same specs.


On 25 Jan, 22:54, Benne <ben.wieg...@gmail.com> wrote:
> I checked the schematics, and the GPIO are set. I don't remember if > they were set low or high now since I am at home sick. But I passed by > my office the other day and checked the schematics in a haste.
When you get back, check two things: 1) Check that the GPIO are set correctly for your application (check both the schematics and the physical device) 2) Check the device for flaws, like bad solders or broken lines. Rune