MSP432 and TI-RTOS: Getting Started Pt. 2 - Add an ADC Sample Task

RE: MSP432 and TI-RTOS: Getting Started Pt. 2 - Add an ADC Sample Task

fredws — Fri, 23 Feb 2018 16:38:40 GMT

Thought while I was at it, I looked at timing in adc routine with printing and without printing.

Routine takes at least 60 microseconds to process an ADC convert routine.

With the print routine, it takes at least 220 microseconds, but not sure if this is just passing the printed value out of the routine or actually finishing printing it out the Serial Port.

I am trying to get 1 millisecond and faster ADC readings using this method on a sampled period, so I am looking at this timing carefully.

So 1/0.000060 seconds = 16,666 readings per second maximum implementing it this way assuming no other interrupts. Obviously, you cannot go this fast if you want your program to do something else.

Red Stars, comment in or comment out for this test, found in the adc_sample.c routine in this pages examples.

[View:/resized-image/__size/620x325/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183765.png:620:325]

[View:/resized-image/__size/677x664/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183766.png:677:664]

RE: MSP432 and TI-RTOS: Getting Started Pt. 2 - Add an ADC Sample Task

fredws — Fri, 23 Feb 2018 15:50:43 GMT

In case anyone is wondering, the clock Module shows the Tick period (us).

This is default to 1000 microseconds per tick generated, or one Tick per millisecond.

This 1 millisecond rate is what Is used as a time source for the Task Argument 0 value in this example.

so ADC Task Argument 0 = 10000 related to 10,000 milliseconds if used with Task_sleep((UInt)arg0);

[View:/resized-image/__size/724x562/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183764.png:724:562]

RE: MSP432 and TI-RTOS: Getting Started Pt. 2 - Add an ADC Sample Task

fredws — Fri, 23 Feb 2018 15:04:36 GMT

=================== added Extra comment with RTOS Execution Graphs ==================

So, RTOS Analyzer - Execution Graph with Argument 0 = 10,000,000

Pulses are spaced 10 seconds apart, graph shows heartBearFxn at 1 second, really can't see taskAdcSample at 10 seconds, but at 30 second mark on graph, if I zoom in, I can see the Adc and heartbeat. I would have to let this run much longer to get more sample to see this.

[View:/resized-image/__size/1014x195/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183761.png:1014:195]

So, RTOS Analyzer - Execution Graph with Argument 0 = 10,000

Pulses are spaced 10 milli-seconds apart

[View:/resized-image/__size/1012x198/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183762.png:1012:198]

You can setup RTOS Analyzer from Tools > RTOS Analyzer > Execution Graph.

You have to run it once to set it up, then the next time it should look like this.

[View:/resized-image/__size/352x384/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183763.png:352:384]

In the .cfg file to enable logging, find the BIOS_logsEnabled = true; and comment It in, comment out the false one.

//BIOS.runtimeCreatesEnabled = false;

/*
* Enable logs in the BIOS library.
*
* Pick one:
* - true (default)
*      Enables logs for debugging purposes.
* - false
*      Disables logging for reduced code footprint and improved runtime
*      performance.
*/
BIOS.logsEnabled = true;
//BIOS.logsEnabled = false;

At end of .cfg file, add this text to get information you are looking for:

// Added at the end of the file
/* FWS commented here and added below for RTOS Analyzer - extra things I added to show on RTOS Execution Graph */
// Select what you want to see in your RTOS Analyzer.
// LoggingSetup.sysbiosTaskLogging = true;    // shows Tasks if true
// LoggingSetup.sysbiosHwiLogging = true;     // shows HWI's and Clock if = true
// LoggingSetup.sysbiosSwiLogging = true;     // shows SWI's if true

/* FWS Add for RTOS Analyzer - also comment in BIOS.logsEnabled = true; comment out =false about line 275 */
var LoggingSetup = xdc.useModule('ti.uia.sysbios.LoggingSetup');
LoggingSetup.sysbiosTaskLogging = true; // optional, shows Tasks if true
// LoggingSetup.sysbiosHwiLogging = true; // optional, shows HWI's and Clock if = true
// LoggingSetup.sysbiosSwiLogging = true; // optional, shows SWI's if true
LoggingSetup.mainLogging = true; // optional, not sure what this logs, FWS. Hoping for IDLE.

LoggingSetup.sysbiosLoggerSize = 1024;
LoggingSetup.loadLogging = false;

RE: MSP432 and TI-RTOS: Getting Started Pt. 2 - Add an ADC Sample Task

fredws — Fri, 23 Feb 2018 14:31:18 GMT

First off, great example.

I started with resource explorer using SimpleLink example as shown.

TI-RTOS Kernel (SYS_BIOS), hello > TI-RTOS > CCS Compiler > hello project.

[View:/resized-image/__size/498x650/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183757.png:498:650]

Alternate Starting Program with TI seems to direct you away from for new projects was the empty project used to start this example under the TI-RTOS for MSP430, there is a MSP432 folder under it.

[View:/resized-image/__size/369x253/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183758.png:369:253]

Problem with 10 second interval in ADC routine.

Note in step 1, previous web site, GUI .cfg shows Argument 0 = 10,000,000

[View:/resized-image/__size/600x337/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183759.png:600:337]

In this web page, step 2, you enter 10000.

[View:/resized-image/__size/545x375/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/contentimage_5F00_183760.png:545:375]

Your Task_Sleep(((UInt)arg0)/Clock_tickPeriod); The Task_Sleep(value); function is using the value entered as system clock period ticks.

so, Clock_tickPeriod is set in GUI .cfg as 1000 microseconds (this is 1 millisecond)

Your Arg0 was set to 10000 in this step.

10000/1000 = 10 milliseconds

If your Arg0 was 10000000 then 10000000/1000 = 10,000 milliseconds or 10 seconds.

You could also change the code to:

Task_Sleep((UInt)Arg0); // this now Sleeps for Arg0 clock tick period, so Arg0=10000, wait 10 seconds.

* ======== taskAdcSample ========
* Open an ADC instance and get a sampling result from a one-shot conversion.
*/
Void taskAdcSample(UArg arg0, UArg arg1)
{
ADC_Handle adc0;
ADC_Handle adc1;
ADC_Params params;
uint16_t adcValue0;
uint16_t adcValue1;
ADC_Params_init(&params);
adc0 = ADC_open(Board_ADC0, &params);
adc1 = ADC_open(Board_ADC1, &params);
while (1) {
Task_sleep(((UInt)arg0) / Clock_tickPeriod);
/* Blocking mode conversion */
ADC_convert(adc0, &adcValue0);
ADC_convert(adc1, &adcValue1);
System_printf("Sample %u:%u\n", adcValue0, adcValue1);
/* SysMin will only print to the console when you call flush or exit */
System_flush();
}
// theoretically close the ADC driver. This code is never reached
// ADC_close(adc0);
// ADC_close(adc1);
}

Note main c file

Task_sleep Is this way.

* ======== heartBeatFxn ========
* Toggle the Board_LED0. The Task_sleep is determined by arg0 which
* is configured for the heartBeat Task instance.
*/
Void heartBeatFxn(UArg arg0, UArg arg1)
{
while (1) {
Task_sleep((UInt)arg0);
GPIO_toggle(Board_LED0);
}
}

Hope this helps others looking at this example.

RE: MSP432 and TI-RTOS: Getting Started Pt. 2 - Add an ADC Sample Task

Jan Cumps — Thu, 11 May 2017 19:39:34 GMT

Debug and real-time scheduling don't play well together. But there's more than that that can go wrong. can you upload your project somewhere? it makes it easier to replicate your situation.

RE: MSP432 and TI-RTOS: Getting Started Pt. 2 - Add an ADC Sample Task

eriklho — Wed, 10 May 2017 21:53:22 GMT

I've been trying to set up the adc program, but whenever I build and go into debug the sampler doesn't wait 10s between each sample. It seems to lock up the system with all the samples. The LED starts to blink really slow. Have no idea why. Tried to replicate what you have done a couple of times without luck.

[View:/resized-image/__size/1600x526/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/5582.contentimage_5F00_183755.png:1600:526]

adc_sample.c

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:3ef06e6b-9b7d-4651-b12d-db8be7f5e991:type=c_cpp&text=%2F*+XDCtools+Header+files+*%2F%0A%23include+%3Cxdc%2Fstd.h%3E%0A%23include+%3Cxdc%2Fruntime%2FSystem.h%3E%0A%23include+%3Cxdc%2Fruntime%2FError.h%3E%0A%0A%0A%2F*+BIOS+Header+files+*%2F%0A%23include+%3Cti%2Fsysbios%2FBIOS.h%3E%0A%23include+%3Cti%2Fsysbios%2Fknl%2FTask.h%3E%0A%23include+%3Cti%2Fsysbios%2Fknl%2FClock.h%3E%0A%0A%0A%2F*+TI-RTOS+Header+files+*%2F%0A%23include+%3Cti%2Fdrivers%2FADC.h%3E%0A%0A%0A%2F*+Example%2FBoard+Header+files+*%2F%0A%23include+%22Board.h%22%0A%0A%0A%2F*%0A+*++%3D%3D%3D%3D%3D%3D%3D%3D+taskAdcSample+%3D%3D%3D%3D%3D%3D%3D%3D%0A+*++Open+an+ADC+instance+and+get+a+sampling+result+from+a+one-shot+conversion.%0A+*%2F%0AVoid+taskAdcSample%28UArg+arg0%2C+UArg+arg1%29%0A%7B%0A++++ADC_Handle+++adc0%3B%0A++++ADC_Handle+++adc1%3B%0A++++ADC_Params+++params%3B%0A++++uint16_t+adcValue0%3B%0A++++uint16_t+adcValue1%3B%0A++++ADC_Params_init%28%26params%29%3B%0A++++adc0+%3D+ADC_open%28Board_ADC0%2C+%26params%29%3B%0A++++adc1+%3D+ADC_open%28Board_ADC1%2C+%26params%29%3B%0A%0A%0A++++while+%281%29+%7B%0A++++++++Task_sleep%28%28%28UInt%29arg0%29+%2F+Clock_tickPeriod%29%3B%0A++++++++%2F*+Blocking+mode+conversion+*%2F%0A++++++++ADC_convert%28adc0%2C+%26adcValue0%29%3B%0A++++++++ADC_convert%28adc1%2C+%26adcValue1%29%3B%0A++++++++System_printf%28%22Sample+%25u%3A%25u%5Cn%22%2C+adcValue0%2C+adcValue1%29%3B%0A++++++++%2F*+SysMin+will+only+print+to+the+console+when+you+call+flush+or+exit+*%2F%0A++++++++System_flush%28%29%3B%0A++++%7D%0A++++%2F%2F+theoretically+close+the+ADC+driver.+This+code+is+never+reached%0A%2F%2F++++ADC_close%28adc0%29%3B%0A%2F%2F++++ADC_close%28adc1%29%3B%0A%7D]

[View:/resized-image/__size/162x226/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-a707f0ba-7c08-4481-8c56-c3e2e4ca3871/4186.contentimage_5F00_183756.png:162:226]

datalogger.c

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:3ef06e6b-9b7d-4651-b12d-db8be7f5e991:type=c_cpp&text=%2F*%0A+*+Copyright+%28c%29+2015%2C+Texas+Instruments+Incorporated%0A+*+All+rights+reserved.%0A+*%0A+*+Redistribution+and+use+in+source+and+binary+forms%2C+with+or+without%0A+*+modification%2C+are+permitted+provided+that+the+following+conditions%0A+*+are+met%3A%0A+*%0A+*+*++Redistributions+of+source+code+must+retain+the+above+copyright%0A+*++++notice%2C+this+list+of+conditions+and+the+following+disclaimer.%0A+*%0A+*+*++Redistributions+in+binary+form+must+reproduce+the+above+copyright%0A+*++++notice%2C+this+list+of+conditions+and+the+following+disclaimer+in+the%0A+*++++documentation+and%2For+other+materials+provided+with+the+distribution.%0A+*%0A+*+*++Neither+the+name+of+Texas+Instruments+Incorporated+nor+the+names+of%0A+*++++its+contributors+may+be+used+to+endorse+or+promote+products+derived%0A+*++++from+this+software+without+specific+prior+written+permission.%0A+*%0A+*+THIS+SOFTWARE+IS+PROVIDED+BY+THE+COPYRIGHT+HOLDERS+AND+CONTRIBUTORS+%22AS+IS%22%0A+*+AND+ANY+EXPRESS+OR+IMPLIED+WARRANTIES%2C+INCLUDING%2C+BUT+NOT+LIMITED+TO%2C%0A+*+THE+IMPLIED+WARRANTIES+OF+MERCHANTABILITY+AND+FITNESS+FOR+A+PARTICULAR%0A+*+PURPOSE+ARE+DISCLAIMED.+IN+NO+EVENT+SHALL+THE+COPYRIGHT+OWNER+OR%0A+*+CONTRIBUTORS+BE+LIABLE+FOR+ANY+DIRECT%2C+INDIRECT%2C+INCIDENTAL%2C+SPECIAL%2C%0A+*+EXEMPLARY%2C+OR+CONSEQUENTIAL+DAMAGES+%28INCLUDING%2C+BUT+NOT+LIMITED+TO%2C%0A+*+PROCUREMENT+OF+SUBSTITUTE+GOODS+OR+SERVICES%3B+LOSS+OF+USE%2C+DATA%2C+OR+PROFITS%3B%0A+*+OR+BUSINESS+INTERRUPTION%29+HOWEVER+CAUSED+AND+ON+ANY+THEORY+OF+LIABILITY%2C%0A+*+WHETHER+IN+CONTRACT%2C+STRICT+LIABILITY%2C+OR+TORT+%28INCLUDING+NEGLIGENCE+OR%0A+*+OTHERWISE%29+ARISING+IN+ANY+WAY+OUT+OF+THE+USE+OF+THIS+SOFTWARE%2C%0A+*+EVEN+IF+ADVISED+OF+THE+POSSIBILITY+OF+SUCH+DAMAGE.%0A+*%2F%0A%0A%0A%2F*%0A+*++%3D%3D%3D%3D%3D%3D%3D%3D+empty.c+%3D%3D%3D%3D%3D%3D%3D%3D%0A+*%2F%0A%2F*+XDCtools+Header+files+*%2F%0A%23include+%3Cxdc%2Fstd.h%3E%0A%23include+%3Cxdc%2Fruntime%2FSystem.h%3E%0A%0A%0A%2F*+BIOS+Header+files+*%2F%0A%23include+%3Cti%2Fsysbios%2FBIOS.h%3E%0A%23include+%3Cti%2Fsysbios%2Fknl%2FTask.h%3E%0A%0A%0A%2F*+TI-RTOS+Header+files+*%2F%0A%23include+%3Cti%2Fdrivers%2FGPIO.h%3E%0A%2F%2F+%23include+%3Cti%2Fdrivers%2FI2C.h%3E%0A%2F%2F+%23include+%3Cti%2Fdrivers%2FSDSPI.h%3E%0A%2F%2F+%23include+%3Cti%2Fdrivers%2FSPI.h%3E%0A%2F%2F+%23include+%3Cti%2Fdrivers%2FUART.h%3E%0A%2F%2F+%23include+%3Cti%2Fdrivers%2FWatchdog.h%3E%0A%2F%2F+%23include+%3Cti%2Fdrivers%2FWiFi.h%3E%0A%0A%0A%2F*+Board+Header+file+*%2F%0A%23include+%22Board.h%22%0A%0A%0A%23define+TASKSTACKSIZE+++512%0A%0A%0ATask_Struct+task0Struct%3B%0AChar+task0Stack%5BTASKSTACKSIZE%5D%3B%0A%0A%0A%2F*%0A+*++%3D%3D%3D%3D%3D%3D%3D%3D+heartBeatFxn+%3D%3D%3D%3D%3D%3D%3D%3D%0A+*++Toggle+the+Board_LED0.+The+Task_sleep+is+determined+by+arg0+which%0A+*++is+configured+for+the+heartBeat+Task+instance.%0A+*%2F%0AVoid+heartBeatFxn%28UArg+arg0%2C+UArg+arg1%29%0A%7B%0A++++while+%281%29+%7B%0A++++++++Task_sleep%28%28UInt%29arg0%29%3B%0A++++++++GPIO_toggle%28Board_LED0%29%3B%0A++++%7D%0A%7D%0A%0A%0A%2F*%0A+*++%3D%3D%3D%3D%3D%3D%3D%3D+main+%3D%3D%3D%3D%3D%3D%3D%3D%0A+*%2F%0Aint+main%28void%29%0A%7B%0A%0A%0A++++%2F*+Call+board+init+functions+*%2F%0A++++Board_initGeneral%28%29%3B%0A++++Board_initGPIO%28%29%3B%0A++++Board_initADC%28%29%3B%0A++++%2F%2F+Board_initI2C%28%29%3B%0A++++%2F%2F+Board_initSDSPI%28%29%3B%0A++++%2F%2F+Board_initSPI%28%29%3B%0A++++%2F%2F+Board_initUART%28%29%3B%0A++++%2F%2F+Board_initWatchdog%28%29%3B%0A++++%2F%2F+Board_initWiFi%28%29%3B%0A%0A%0A%0A%0A%0A%0A++++%2F*+Turn+on+user+LED+*%2F%0A++++GPIO_write%28Board_LED0%2C+Board_LED_ON%29%3B%0A%0A%0A++++System_printf%28%22Starting+the+example%5CnSystem+provider+is+set+to+SysMin.+%22%0A++++++++++++++++++%22Halt+the+target+to+view+any+SysMin+contents+in+ROV.%5Cn%22%29%3B%0A++++%2F*+SysMin+will+only+print+to+the+console+when+you+call+flush+or+exit+*%2F%0A++++System_flush%28%29%3B%0A%0A%0A++++%2F*+Start+BIOS+*%2F%0A++++BIOS_start%28%29%3B%0A%0A%0A++++return+%280%29%3B%0A%7D]