Sign in
Search c54x
Subscribe to c54x
c54x by Keywords
5409 | 5416 | AD5 | ADC | BIOS | Boot | Booting | Bootloader | C540 | C5402 | C5409 | C5416 | CCS | Codec | DMA | Dmad | DSK | DSKPlus | Dsplib | EVM | FFT | FIR | Flash | GPIO | HPI | Initialization | Interrupt | JTAG | LOG_printf | MCBSP | RFFT | RTDX | Sampling | STLM | UART | VC540
Sponsor
Discussion Groups
See Also
Discussion Groups | TMS320C54x | SPI mode for 5409 (again)
Technical discussions about the TI C54x DSPs (including the c5401, c5402, c5402a, c5404, c5407, c5409, c5409a, c5410, c5410a, c5416, c5420, c5421, c5441, c549, c5470 and c5471).
SPI mode for 5409 (again) - nikhil rao - Jan 6 7:23:00 2001
|
The receive part of the SPI protocol does not work for me.. I have set up my registers exactly as described in the manual. In the spi mode are we supposed to read from the serial port like x = *((unsigned char *) 0x31) should this generate chip select and clock signals. I have noticed that this doesnt. So what I did was to generate these signals using a write and I noticed that the value to be read back was in DRR1..the MCBSP window in Code composer tells me this. however if I try to read the value by doing x = *((unsigned char *) 0x31) I get some junk values. Examining the memory using code composer also shows me the correct value... Thanks, nikhil |
|
|
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.
(You need to be a member of c54x -- send a blank email to c54x-subscribe@yahoogroups.com )
Re: SPI mode for 5409 (again) - Brian C. Lane - Jan 8 17:29:00 2001
|
On Sat, 06 Jan 2001 07:23:12 -0000, you wrote:
>The receive part of the SPI protocol does not work for me.. >I have set up my registers exactly as described in the manual. In the >spi mode are we supposed to read from the serial port like > x = *((unsigned char *) 0x31) >should this generate chip select and clock signals. I have noticed >that this doesnt. In c54regs.h it has this definition for DXR1 - #define DXR1 *(volatile unsigned int *)0x31 You have to define it as a volatile so that the compiler doesn't try to optimize it in some way. Take a look at the definitions in the included header files, there are a whole bunch of useful macros, etc. Brian ----------------------------------------------------- Brian C. Lane Programmer www.shinemicro.com RF & Microcontroller Design |
(You need to be a member of c54x -- send a blank email to c54x-subscribe@yahoogroups.com )