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
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.
Telkom Development Laboratory
Telkom SA _____________________________________
Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you
want your answer to be distributed to the entire group.
About this discussion group:
More Groups: http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/