Robert-
> I don't think there are any 3rd party HPI
boards either, to communicate to
> the host for the 6713 DSK. But there might be a market for it ...
including
> me, if it could support rates high enough.
>
> About 3. below, thats what I really need for the 6713 DSK!! ( access to
the
> board from the host via a MS VC++ DLL, examples, etc ). Unfortunately,
TI
> decided not to go that support route with it. The 6711 DSK has
> disadvantages relative to the 6713 DSK though too including being
slower
> and code size limited.
This question has come up a few times -- including your post on Feb 8. I
answered
the next day (copy below), but I got no takers or even solid interest, students
or
otherwise. So if there's a market, it's a darn hard one to see.
-Jeff
-------- Original Message --------
Subject: Re: [code-comp] TMS320C6713 board loader
Date: Wed, 09 Feb 2005 08:24:24 -0600
From: Jeff Brower <>
Organization: Signalogic, Inc
To: Bhooshan Iyer <>
CC: robert <>, ,,
Bhooshan-
> Anyways, many of the early attempts at having a
non-CCS development
> methodologies seem to have fallen by the way. Among the few remaining
> non-CCS options what i would recommend is a software program called
> DirectDSP made by one of our list's active member's
> company-Signalogic. Not sure though if DirectDSP supports c6713 but
> may be signalogic could help you on that.
>
> http://www.signalogic.com/index.pl?page=directDSP
As the "keeper" of DirectDSP software, I can say this:
1) It does not support C6713 DSK board because the combined USB-JTAG interface
is
slow, around 20-30 kbyte/sec. Neither USB or JTAG by itself should be that slow,
but
it's something in the Spectrum Digital implementation. I'm sure they
could have made
it faster, but as you say, that is not TI's purpose in making inexpensive
DSK boards
that provide both showcase and reference design for their chips.
2) If someone on the group can make an HPI daughtercard for the DSK board and
show
basic HPI register-level connectivity from a simple C program, then we can port
the
parallel port driver in DirectDSP to it. Such a daughtercard would look
something
like this:
__ HPI-PP daughtercard
__________/
___| \______/ |______
| | | |
| ========== <--------- HPI connector
| |
| || || |
| || ||<-------- standard daughtercard connectors
| || || |
| || || | <-- "new style" DSK board
The HPI-PP daughtercard must:
-be small and super cheap
-have standard DB25 male connector, as on DSK 6711
-not overlap the main daughtercard area of the DSK board;
i.e. the board-to-board connector should be as close to
the edge of the PCB as possible
-have mounting standoffs at corners with height that
reaches to the surface the DSK board is resting on
(to provide strain relief on the board-to-board
connector). Mounting holes -- or some mechanical
method -- to the DSK board itself would be better,
but SD has not allowed for that
-provide 8-bit access to HPI registers in EPP and
EPP+ECP PP modes. That means the daughtercard needs
a small CPLD with state-machine that:
-on writes, aggregates even + odd bytes then issues
16-bit write to HPI
-on reads, makes 16-bit HPI read, sends even byte to
parallel port, stores odd byte for next PP read
the state machine should reset HHWIL signal to zero
as often as possible; e.g. on Reset, on two consecutive
even or odd accesses, etc.
-provide Reset control over the C6713, in addition to
HPI register access
-provides 5V to 3.3V translation, provides series R
protection for PP lines, etc. We can review the
schematic...
We keep thinking this is a great student-level project, but we keep finding
production level design things to put our entry-level engineers to work on, so
the
HPI-PP daughtercard project never gets traction. To put that another way,
it's a fun
project, but not very attractive commercially.
DirectDSP has both WinXP and Linux drivers, PP and PCI. Basically any time the
HPI
is accessible.
-Jeff
> On Tue, 8 Feb 2005 18:50:37 -0600, robert <>
wrote:
> >
> >
> > Yes, I have come across this problem too. I had planned on using a
VC++
> > program, to load the 6713 DSK … but have found out, like you,
that CCS needs
> > to used unfortunately to load it. I guess the 6711 DSK had direct
API's
> > that could be called to load and run the board, but that functionality
for
> > some reason has been left out of the 6713 DSK. It might be something
about
> > the USB connection.
> >
> > But I'd be interested if anyone has any ideas on this as well.
> >
> > One possibility, I guess, is to try and use RS-232 from the PC side to
a
> > McBSP on the 6713. Someone had suggested "hyper access" for
this, which
> > costs about $100. On the DSK side, the flash would have to be
programmed
> > with some kind of initial bootup, where it configures the McBSP and
> > implements the software UART. And once that is running, the code could
be
> > loaded. But that's a lot more effort than anticipated!, if it
works.
> >
> > Regards,
> >
> > Robert
> >
> > _____
> >
> > From: [mailto:]
> > Sent: Tuesday, February 08, 2005 7:44 AM
> > To:
> > Subject: [code-comp] TMS320C6713 board loader
> >
> >
> > --- This message has also been posted in TMS320C6x -----
> >
> > Hi all,
> >
> > I\'m new on this list and I will really appreciate any help with
this
> > problem as it is halting all my work.
> >
> > I have recently purchased a TMS320C6713 board and I have found out
that
> > there is no command (DOS) for loading a program onto this board and
the IDE
> > of the Code Composer Studio becomes necessary. As I have to run
many
> > experiments
> > (hundreds of thousands) this option becomes infeasible. I have tried
using
> > gel files (as start up) but for some reason the instructions do not
> > execute sequencially. Another option is using the libraries for perl
but
> > unfortunately they do not come with the version of the CCS that is
> > included in the kit.
> >
> > Has anyone come across the same problem?
> >
> > I look forward to hearing from you.
> >
> > Cheers,
> > ---
> > Edwin
|