Other Parts Discussed in Thread: SYSBIOS
I am using tirtos_simplelink_2_13_00_06 and added some SPI reading.writing code to one of the examples (SensorTag). Specifically, the init function of the SensorTag task. The reading and writing via SPI works as expected. If i move this code to the init function (or anywhere else) of that task, the SPI read/write fails (the data i read i bogus).
I verified that the priority and stack size of the 2 tasks are identical but can not understand why that SPI reading works in one but not the other. One difference is that my task is statically created in .cfg while the SensoTag example task is created dynamically in code.
While i used the BLE SensorTag example for this test, this is, i suppose, more of a general TIRTOS question and therefore i decided to post it here.
Does anyone have some hint what could cause this?
void myTaskFunc(UArg a0, UArg a1) {
bspSpiOpen();
setupFRAM(); //setup CS for this SPI memory
testFRAM(); //SPI r/w fails here
// Task loop
while (true) { ... }
}
static void SensorTag_taskFunc(UArg a0, UArg a1) {
bspSpiOpen();
setupFRAM(); //setup CS for this SPI memory
testFRAM(); //SPI r/w works here
// Task loop
while (true) { ... }
}

