Add SCI to Motorware example project

There is not an InstaSPIN library for SCI, there are SCI drivers / API created in MotorWare

C:\ti\motorware\motorware_1_01_00_08\sw\drivers\sci\src\32b\f28x\f2806x

The easiest way to browse the functions is to use C:\ti\motorware\motorware_1_01_00_08\MotorWare.exe

and go to Drivers --> API Documentation

In the MotorWare projects (sw/solutions) we don't have an example of using the SCI (UART) because we typically have JTAG on the controlCARD for development and use SPI or GPIO to talk to power drivers.  On the thread you mention I posted an example (ate_comms.zip) of using UART that we do use on our automated test equipment, just to give an idea of how the SCI is set-up and commands are used.

I would use the MotorWare APIs to accomplish your goal, NOT the controlSUITE example.

Thank you, Chris! This is exactly what I need!

Hi Maria, did this work for you? I see that some library functions are missing in the Motorware modules compared to C200 Launchpad modules.

-Tamil

Hello Tamil,

I haven't tried it yet. Previously I only learned how to configure the registers because I am new in TI microcontroler (how to set the registers manually, and how to adapt them in Motorware).

Seems that the one in launchpad is easier to be used because we only need to set the registers.

In Motorware, we can call the functions we need, but indeed some of them are missing (but I don't know in latest Motorware).

Soon, I will have time to try this SCI. Now I have holiday until next week so I could not try it.

I will inform you later.

Meanwhile, hope you can solve your problem.

Best regards,

Maria

Tamil,

When I compare the controlSUITE LaunchPad version vs. MotorWare, I see the exact same sci API functions defined. There is only one small difference with one API:

controlSUITE version:

void SCI_setTxDelay(SCI_Handle sciHandle, const uint8_t delay)

MotorWare version:

void SCI_setTxDelay(SCI_Handle sciHandle, const uint_least8_t delay)

what functions do you think are missing?

Thanks for your reply Maria.

Chris, I have started another thread describing my issue. Thanks for your help.

-Tamil

I too am integrating SCI unto my project through the F28609M control card.

I am looking at the code from controlsuite and ported over the example the best I could to motorware 12.

I created interrupt functions for both rx and tx sci interrupts but they never seem to go to them. Both the ate example and the controlsuite example seem to process all sci data in non-interrupt functions. Am I right in saying that?

I've been pulling my hair to figure out why. Hopefully I can get answer.

Cristhian

Hello Christian,

I would like you to check this thread.

http://e2e.ti.com/support/microcontrollers/c2000/f/902/p/334989/1168654.aspx#1168654

Hope this helps you.

Best regards,

Maria

Trey,

Yes, that was the case. I figured it out an hour after I posted the question. I forgot to enable the PIE. Thanks.

Cristhian

Even after enabling my PIE, my interrupts don't seem to process. My device seems to be halting. Should I bother using interrupts?

When clearing the interrupt flag, the only on I see cleared it the INT9 group. Why doesn't RXFFINT CLR get used? When I did so, it halted my program. When I attempt to debug on the interrupt, I get no assembly error.

I've seen examples where all the SCI data processing is done in main loop. Should that be the way to do it?

Here is my code this far. My GPIOs are set up as GPIO 28 for RX, 29 for TX, no pullups or input qual. The async was giving me a problem:

void HAL_setupScia(HAL_Handle handle){
	HAL_Obj *obj = (HAL_Obj *)handle;

	// setup communication mode & parameters - idle-line,115200,8,N,1
	SCI_setNumStopBits(obj->sciHandle,SCI_NumStopBits_One);		// clr SCICCR bit 7
	SCI_setParity(obj->sciHandle,SCI_Parity_Odd);				// clr SCICCR bit 6
	SCI_disableParity(obj->sciHandle);							// clr SCICCR bit 5
	SCI_disableLoopBack(obj->sciHandle);						// clr SCICCR bit 4
	SCI_setMode(obj->sciHandle,SCI_Mode_IdleLine);				// clr SCICCR bit 3
	SCI_setCharLength(obj->sciHandle,SCI_CharLength_8_Bits);	// set SCICCR bits 2..0
	SCI_setBaudRate(obj->sciHandle,SCI_BaudRate_115_2_kBaud);	// SCIHBAUD:SCILBAUD

	SCI_disable(obj->sciHandle);								// clr SCICTL1 bit 5
	SCI_enableRx(obj->sciHandle);								// set SCICLT1 bit 0
	SCI_enableTx(obj->sciHandle);								// set SCICLT1 bit 1
	SCI_enableRxInt(obj->sciHandle);							// set SCICTL2 bit 1
//	SCI_enableTxInt(obj->sciHandle);							// set SCICTL2 bit 0

	// set up FIFOs
	SCI_enableChannels(obj->sciHandle);							// set SCIFFTX bit 15
	SCI_enableTxFifoEnh(obj->sciHandle);						// set SCIFFTX bit 14
	SCI_resetTxFifo(obj->sciHandle);							// set SCIFFTX bit 13
	SCI_disableTxFifoInt(obj->sciHandle);						// clr SCIFFTX bit 5
	SCI_setTxFifoIntLevel(obj->sciHandle,SCI_FifoLevel_Empty);	// SCIFFTX bits 4..0

	SCI_enableRxFifo(obj->sciHandle);							// set SCIFFRX bit 13
	SCI_enableRxFifoInt(obj->sciHandle);						// clr SCIFFRX bit 5
	SCI_setRxFifoIntLevel(obj->sciHandle,SCI_FifoLevel_Empty);	// SCIFFRX bits 4..0

	SCI_setTxDelay(obj->sciHandle,0);
	SCI_setPriority(obj->sciHandle,SCI_Priority_FreeRun);
	SCI_enable(obj->sciHandle);									// set SCICTL1 bit 5
	return;
} // end of HAL_setupScia() function

void HAL_enableSciaInt(HAL_Handle handle){
	HAL_Obj *obj = (HAL_Obj *)handle;

	PIE_enableRxInt(obj->pieHandle);		// INT9.1
	//PIE_enableTxInt(obj->pieHandle);		// INT9.2
	CPU_enableInt(obj->cpuHandle,CPU_IntNumber_9);	// enable cpu interrupt group for Rx & Tx
	return;
} // end of HAL_enableSciaInt() funtion

interrupt void uartRxISR(void){
	HAL_acqRxInt(halHandle);

	HAL_Obj *obj = (HAL_Obj *)halHandle;
	uint16_t rxChar = SCI_read(obj->sciHandle);
	SCI_write(obj->sciHandle,rxChar);
	rxBuffer[rxBufIndex++] = rxChar;

	return;
} // end of uartRxISR() function

static inline void HAL_acqRxInt(HAL_Handle handle){
	HAL_Obj *obj = (HAL_Obj *)handle;

	//SCI_clearRxFifoInt(obj->sciHandle);			// clear fifo interrupt flag from SCIFFRX <- GIVES ERROR AND HALTS
	//SCI_clearRxFifoOvf(obj->sciHandle);			// clear overflow interrupt flog from SCIFFRX
	PIE_clearInt(obj->pieHandle,PIE_GroupNumber_9);		// acknowledge interrupt from PIE group 9
	return;
}

Cristhian

Cristhian Arbelaez said:

SCI_enableTxFifoEnh(obj->sciHandle); // set SCIFFTX bit 14

Not sure 100% but this call somehow prevents Rx interrupt to occur.

At least, that was what I saw. In my program I only allow Rx int but not Tx int.

Tinhtan,

I ended up scrapping FIFOs and going with straight RX interrupts. Thank you for you response.

Cristhian

Hi Chris ,

Could you please share me the ate_comms.zip that you mentioned ? Or please email me to yzhan125@gmail.com ?

I'm currently working on the instaSPIN-FOC development kit, trying to figure out a way to automate test through UART like yous. 

Thanks,

Jess

Hi Chris, 

I'm trying to run the demo on F28027 lunch pad and trying to see if the communication works there. 

I think the first time it does work and I saw the temperature changing through Putty. But then second time I try, I got lots of error message while compile. 

It's really confusing, could you please let me know where it went wrong? I attached error and compile properties in below: 

Did you add any additional constants, such as an array of values? Either way, if you look at the memory map, you'll see that you have a specific amount of RAM to work with. Here, it's broken up into 3 sections: RAMM1, RAMM0, and DRAML0. You'll see that RAMM0 and DRAML0 are continuous, i.e. you can pull from one to increase the other. You'll see that RAMM0 starts at 0x8000 and has length of 0x900; furthermore, DRAML0 starts at 0x8900 (0x8000+0x900 from RAMM0), and has length of 0x700 (ending at 0x9000). You can reduce the size of RAMM0 (by decreasing it's length), and reassign a new starting address to DRAML0 equal to what you took from RAMM0.

In general, you can see what you have available overall on page 46 of this document: www.ti.com/.../sprs523k.pdf

You'll see that RAMM0 and DRAML0 effectively cover the whole "L0 SARAM (4K x 16)" block of RAM starting from 0x8000. You can allocate that however you'd like. And yes, any other project that links to this linker command file will have the same memory allotments made. You can create a .cmd file specifically for one project if you'd like.

Sean