Sign in

username:

password:



Not a member?

Search motoroladsp



Search tips

Subscribe to motoroladsp



motoroladsp by Keywords

56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Discussion Groups

Discussion Groups | Freescale DSPs | Bug in SDK 2.4

Technical discussions about Freescale (Motorola) DSPs (including the DSP56000, DSP56300, DSP56600, 56800 DSPs).

  

Post a new Thread

Bug in SDK 2.4 - Roelof Oelofsen - May 22 11:04:00 2002



Hi everyone,

There is a bug (hopefully not one in many!!) in SDK2.4. (I am using the
56f807evm) When using the GPIO Api's, it does not want to work if
gpio.h or io.h is included. It will only work when led.h is included.
Also, when I include switch.h, the compiler give a string of errors
which are mostly in the header file! (Bug no.2). If my findings is
incorrect, please let me know and also why it is like this.

Also be ware that when you use the user leds, that GPIOB0 -> GPIOB2
will be unavailable as inputs because the leds use them.

Regards
Roelof Oelofsen
Telkom Development Laboratory
Telkom SA






(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

RE: Bug in SDK 2.4 - Roberts, Drew - May 23 12:22:00 2002

Roelof

I have not tried using the GPIO Api's without led.h since I use the LED
functions. It is true that the user leds are set to port b pins, but since
you have the source code you can modify what pins are used. I beleive
somewhere in Motorolas documentation they mention that the SDK is a starting
point and that they assume the user will eventually modify/cusomize the
functions. Just another note in the SPI handler, the provided SDK functions
always set up a GPIO pin for the chip select, even if you are using your own
select functions. You need to modify the code so it will only setup the pin
if you use the default chip select -----Original Message-----
From: Roelof Oelofsen [mailto:]
Sent: Wednesday, May 22, 2002 7:04 AM
To:
Subject: [motoroladsp] Bug in SDK 2.4 Hi everyone,

There is a bug (hopefully not one in many!!) in SDK2.4. (I am using the
56f807evm) When using the GPIO Api's, it does not want to work if
gpio.h or io.h is included. It will only work when led.h is included.
Also, when I include switch.h, the compiler give a string of errors
which are mostly in the header file! (Bug no.2). If my findings is
incorrect, please let me know and also why it is like this.

Also be ware that when you use the user leds, that GPIOB0 -> GPIOB2
will be unavailable as inputs because the leds use them.

Regards
Roelof Oelofsen
Telkom Development Laboratory
Telkom SA _____________________________________
/groups.php3





(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )