Sign in
Search c55x
Subscribe to c55x
c55x by Keywords
AIC23 | C5509 | CCS | CSL | EMIF | EVM | GEL | GPIO | HPI | Interfacing | JTAG | McBSP | OMAP | Omap15 | OMAP59 | RTDX | SDRAM | TMS320VC5509 | USB | XDS5
Discussion Groups
Discussion Groups | TMS320C55x | stdio functions not working on dsk5510 with dsk_app1.pjt
Technical discussions about the TI C55x DSPs (including the c5501, c5502, c5503, c5507, c5509, c5510 and OMAP5910).
stdio functions not working on dsk5510 with dsk_app1.pjt - esye...@sandia.gov - Jan 4 18:00:00 2006
Jeff/Nanna,
I am having problems with using printf and scanf as well. I am using the dsk_app1.pjt used in the tutorial. I have the DMA setup to send audio out of the codec. However, I'd like to use scanf and printf to modify certain parameters.
I experience linking problems when I try to include rts55.h to the project.
thanks,
Steve
(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )
Re: stdio functions not working on dsk5510 with dsk_app1.pjt - Jeff Brower - Jan 6 15:04:00 2006
Steve-
> I am having problems with using printf and scanf as well. I am using the
> dsk_app1.pjt used in the tutorial. I have the DMA setup to send audio out
> of the codec. However, I'd like to use scanf and printf to modify certain
> parameters.
Ok, but this is not a simulator issue if you are using a DSK board. In that case,
I/O commands that require JTAG communication with the PC are known to encounter
problems when they fight for CPU cycles with real-time ISR code, DMA transfers, etc.
I think solving the simulator problem with I/O commands first would be a good idea,
it should be a lot easier.
> I experience linking problems when I try to include rts55.h to the project.
This should be a separate thread... please post some details.
-Jeff
(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )
> I am having problems with using printf and scanf as well. I am using the
> dsk_app1.pjt used in the tutorial. I have the DMA setup to send audio out
> of the codec. However, I'd like to use scanf and printf to modify certain
> parameters.
Ok, but this is not a simulator issue if you are using a DSK board. In that case,
I/O commands that require JTAG communication with the PC are known to encounter
problems when they fight for CPU cycles with real-time ISR code, DMA transfers, etc.
I think solving the simulator problem with I/O commands first would be a good idea,
it should be a lot easier.
> I experience linking problems when I try to include rts55.h to the project.
This should be a separate thread... please post some details.
-Jeff
(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )
RE: stdio functions not working on dsk5510 with dsk_app1.pjt - Logan, Tammy - Jan 9 16:40:00 2006
Personally, I would recommend not using generic IO commands. They are
almost always either non-existent or problematic in embedded code. For
TI, use their LOG_printf facility. It also runs much faster. If you want
some compatibility, then simply use a macro to hide the TI usage. Scanf
may be a bigger problem, but I believe they do have another way to feed
data to the dsk. -----Original Message-----
From: c55x@c55x... [mailto:c55x@c55x...]
Sent: Saturday, January 07, 2006 5:41 AM
To: c55x@c55x...
Subject: [c55x] Digest Number 424
There is 1 message in this issue.
Topics in this digest:
1. Re: stdio functions not working on dsk5510 with dsk_app1.pjt
From: Jeff Brower <jbrower@jbro... ________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Fri, 06 Jan 2006 13:04:09 -0600
From: Jeff Brower <jbrower@jbro...>
Subject: Re: stdio functions not working on dsk5510 with dsk_app1.pjt
Steve-
> I am having problems with using printf and scanf as well. I am using
> the dsk_app1.pjt used in the tutorial. I have the DMA setup to send
> audio out of the codec. However, I'd like to use scanf and printf to
> modify certain parameters.
Ok, but this is not a simulator issue if you are using a DSK board. In
that case, I/O commands that require JTAG communication with the PC are
known to encounter problems when they fight for CPU cycles with
real-time ISR code, DMA transfers, etc.
I think solving the simulator problem with I/O commands first would be a
good idea, it should be a lot easier.
> I experience linking problems when I try to include rts55.h to the
project.
This should be a separate thread... please post some details.
-Jeff
(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )
almost always either non-existent or problematic in embedded code. For
TI, use their LOG_printf facility. It also runs much faster. If you want
some compatibility, then simply use a macro to hide the TI usage. Scanf
may be a bigger problem, but I believe they do have another way to feed
data to the dsk. -----Original Message-----
From: c55x@c55x... [mailto:c55x@c55x...]
Sent: Saturday, January 07, 2006 5:41 AM
To: c55x@c55x...
Subject: [c55x] Digest Number 424
There is 1 message in this issue.
Topics in this digest:
1. Re: stdio functions not working on dsk5510 with dsk_app1.pjt
From: Jeff Brower <jbrower@jbro... ________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Fri, 06 Jan 2006 13:04:09 -0600
From: Jeff Brower <jbrower@jbro...>
Subject: Re: stdio functions not working on dsk5510 with dsk_app1.pjt
Steve-
> I am having problems with using printf and scanf as well. I am using
> the dsk_app1.pjt used in the tutorial. I have the DMA setup to send
> audio out of the codec. However, I'd like to use scanf and printf to
> modify certain parameters.
Ok, but this is not a simulator issue if you are using a DSK board. In
that case, I/O commands that require JTAG communication with the PC are
known to encounter problems when they fight for CPU cycles with
real-time ISR code, DMA transfers, etc.
I think solving the simulator problem with I/O commands first would be a
good idea, it should be a lot easier.
> I experience linking problems when I try to include rts55.h to the
project.
This should be a separate thread... please post some details.
-Jeff
(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )
Re: stdio functions not working on dsk5510 with dsk_app1.pjt - Jeff Brower - Jan 10 11:04:00 2006
Tammy-
> Personally, I would recommend not using generic IO commands. They are
> almost always either non-existent or problematic in embedded code. For
> TI, use their LOG_printf facility. It also runs much faster. If you want
> some compatibility, then simply use a macro to hide the TI usage. Scanf
> may be a bigger problem, but I believe they do have another way to feed
> data to the dsk.
If you extend this thinking, then at some point JTAG and RTDX overall are not the way
to go either for real-time debug and data transfer. Both methods impose internal CPU
cycle and bus bandwidth penalties that are hard to characterize and predict, and not
well-documented. Like a Heisenberg uncertainty principle for real-time code
measurement. HPI or other method also has a performance impact, but they are easier
to understand how and when, and can be easily synchronized with running code.
-Jeff
> -----Original Message-----
> From: c55x@c55x... [mailto:c55x@c55x...]
> Sent: Saturday, January 07, 2006 5:41 AM
> To: c55x@c55x...
> Subject: [c55x] Digest Number 424
>
> There is 1 message in this issue.
>
> Topics in this digest:
>
> 1. Re: stdio functions not working on dsk5510 with dsk_app1.pjt
> From: Jeff Brower <jbrower@jbro...>
>
> ________________________________________________________________________
> ________________________________________________________________________
>
> Message: 1
> Date: Fri, 06 Jan 2006 13:04:09 -0600
> From: Jeff Brower <jbrower@jbro...>
> Subject: Re: stdio functions not working on dsk5510 with dsk_app1.pjt
>
> Steve-
>
> > I am having problems with using printf and scanf as well. I am using
> > the dsk_app1.pjt used in the tutorial. I have the DMA setup to send
> > audio out of the codec. However, I'd like to use scanf and printf to
> > modify certain parameters.
>
> Ok, but this is not a simulator issue if you are using a DSK board. In
> that case, I/O commands that require JTAG communication with the PC are
> known to encounter problems when they fight for CPU cycles with
> real-time ISR code, DMA transfers, etc.
>
> I think solving the simulator problem with I/O commands first would be a
> good idea, it should be a lot easier.
>
> > I experience linking problems when I try to include rts55.h to the
> project.
>
> This should be a separate thread... please post some details.
>
> -Jeff >
(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )
> Personally, I would recommend not using generic IO commands. They are
> almost always either non-existent or problematic in embedded code. For
> TI, use their LOG_printf facility. It also runs much faster. If you want
> some compatibility, then simply use a macro to hide the TI usage. Scanf
> may be a bigger problem, but I believe they do have another way to feed
> data to the dsk.
If you extend this thinking, then at some point JTAG and RTDX overall are not the way
to go either for real-time debug and data transfer. Both methods impose internal CPU
cycle and bus bandwidth penalties that are hard to characterize and predict, and not
well-documented. Like a Heisenberg uncertainty principle for real-time code
measurement. HPI or other method also has a performance impact, but they are easier
to understand how and when, and can be easily synchronized with running code.
-Jeff
> -----Original Message-----
> From: c55x@c55x... [mailto:c55x@c55x...]
> Sent: Saturday, January 07, 2006 5:41 AM
> To: c55x@c55x...
> Subject: [c55x] Digest Number 424
>
> There is 1 message in this issue.
>
> Topics in this digest:
>
> 1. Re: stdio functions not working on dsk5510 with dsk_app1.pjt
> From: Jeff Brower <jbrower@jbro...>
>
> ________________________________________________________________________
> ________________________________________________________________________
>
> Message: 1
> Date: Fri, 06 Jan 2006 13:04:09 -0600
> From: Jeff Brower <jbrower@jbro...>
> Subject: Re: stdio functions not working on dsk5510 with dsk_app1.pjt
>
> Steve-
>
> > I am having problems with using printf and scanf as well. I am using
> > the dsk_app1.pjt used in the tutorial. I have the DMA setup to send
> > audio out of the codec. However, I'd like to use scanf and printf to
> > modify certain parameters.
>
> Ok, but this is not a simulator issue if you are using a DSK board. In
> that case, I/O commands that require JTAG communication with the PC are
> known to encounter problems when they fight for CPU cycles with
> real-time ISR code, DMA transfers, etc.
>
> I think solving the simulator problem with I/O commands first would be a
> good idea, it should be a lot easier.
>
> > I experience linking problems when I try to include rts55.h to the
> project.
>
> This should be a separate thread... please post some details.
>
> -Jeff >
(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )