Hi,
Making good progress using 'UDPEchoCC3X00' as my template and adapting for my application however having issues with some conflicts particularly using the LP LEDs and the System Console.
In the 'Board.h' file there is the comment:
/*
* CC3200_LAUNCHXL_LED_D5 and CC3200_LAUNCHXL_LED_D6 are shared with the I2C
* and PWM peripherals. In order for those examples to work, these LEDs are
* taken out of gpioPinCOnfig[]
*/
This is further reflected in the 'CC3200_LAUNCHXL' files.
Also in the
'TI-RTOS 2.16 for CC32xx SimpleLink™
Wireless MCUs
Getting Started Guide'
it states in Section 3.4:
— PWM. The PWM driver uses the onboard LEDs D5 (PIN 02) and D6 (PIN 01). While these pins
coincide with GPIO driver pins, they are configured for the PWM driver for the PWM examples.
The GPIO driver APIs should not be used.
However in the UDPEcho readme.txt file this example is also using Board_LED1 which is D6 above (clearly using GPIO mode) ???
While I'd like to use all LEDs in my application I understand you can't use the same pin for separate things at the same time so I'm content to just use Board_LED0 (D0) and the System Console to help me run and debug my application. Problem is I also see conflict on D0 whenever the system console writes a message. I know this as I set up a highest priority clock (8KHz using clock module) and the ISR calls GPIO_toggle(Board_LED0) and I see the clock corrupted (scope probe on P3.9 on LP) when outputing to the system console. Also if I stop output to the system console then the clock is completely clean and uncorrupted.
Can someone clarify the interactions going on here:
- What signals does the System Console use and how do they conflict with LP LEDs/other ?
- what signals do the I2C/PWM examples use (I think I know but be good to restate)
Any other guidelines most welcome.
best regards,
Stuart
Edinburgh. UK.