rtel wrote on Tuesday, October 26, 2004:
> comtest: got no loop back connector, would like
> to see some ‘hello task1’ messages instead
For the loop back all you need to do is connect pins 2 and 3 - a paper clip is usually sufficient.
Other than that connect a dumb terminal to the port and you will be able to see the characters transmitted even though the task ‘fails’ as nothing is being received.
If nothing is transmitted then it may be that the baud rate setting is slightly wrong - which won’t be noticed when looping back.
>needed to change register names in serial.c in
>order to compile but I don’t think it’s working yet
The 128 has some different setup required for the clock to generate the tick, but I’m not sure about the serial port.
>integer: the computed results seem to be
>different, don’t know why yet
Don’t know why this would be.
I haven’t done a ATMega128 port as the connector for the STK500 is too expensive. Is there a device that will fit straight into the STK500 that has all the same register settings/architecture as the 128? If so I can generate a complete port ready for download.
>Why don’t you use uint8_t etc. for portable
The convention used is just one I have used for years. I prefer to keep the ‘unsigned’ part of the definition as a C keyword rather than incorporating it into the typedef. Most people I come accross have their own conventions.