westmorelandeng wrote on Friday, February 02, 2007:
> c:\TI_U64_Demo\readme.txt says:
"Note: The kernel contained in this port is for 4.0.2 - the other code is 4.0.1"
The zip file that you’ve found wasn’t meant for release - the note above is from an older post and doesn’t apply.
> Using c:\TI_U64_Demo\FreeRTOSv401\FreeRTOS_MSP_Port.eww
I was able to build the execuatble and load onto softBaugh board and able to run the demo. (with few lines of change…)
using IAR work bench.
Good to hear you’ve got it working.
> I notice xAreComTestTasksStillRunning() always returning pdFALSE.
Hence task vErrorChecks() calls
vParTestToggleLED(mainCHECK_LED ) which I have enabled to blink an LED properly.
Not sure about this since I didn’t intend this for release…
> When I furthur traced the code,
interrupt function vRxISR() is kicked when a chacter is received in U1RXBUF with a new character. Like wise vRxISR()interrupt function is called when U1TXBUF is empty and the chracter received is sent out. This is in spite of nothing is physically connected to UART1 port on the board!!
Yep - that’s how the serial port demo. works - it’s in loopback mode. Real useful for test purposes.
> The charcter received and sent are sequential ascii characters don’t know how they are getting in. Have you come across any such?
Yes - that’s the serial port demo.
> I want to be able to connect UART1 to COM port on the PC and be able to send and receive data. besides setting UART1 port, is there anything else I need to be aware of??
Yes - you need to be aware that the serial port code is just for demo. purposes - it isn’t a full-blown serial port implementation. You’ll probably be able to see the loop-backed characters but you won’t be able to send any commands to the UART with the demo. code unless you add that code yourself.
> Also have you exercised tracecon exe files? in
FreeRtosconfig.h I have defined configUSE_TRACE_FACILITY as 1.
Yes - I’ve used this tool - see the FreeRTOS web-site for good instructions. You’ll need to assign a buffer space and then you have to take a look at the buffer with a debugger. If memory serves me - you’ll need a good hex editor - copy from the IAR memory window, put it into a hex editor, and then you can run the utility provided by Richard if I’m remembering this process correctly - anyway, it’s on the web-site.
I posted some code for a colleague some time ago - sounds like this is the zip file that I posted for them. I’m glad you’ve found it useful.