Got the demo working for ATMega 128, except comtest and integer.
comtest: got no loop back connector, would like to see
some 'hello task1' messages instead anyway
needed to change register names in serial.c in order to compile but I don't think it's working yet
integer: the computed results seem to be different, don't know why yet
Why don't you use uint8_t etc. for portable types?

> comtest: got no loop back connector, would like
> to see some 'hello task1' messages instead
> anyway

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
types?

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.

integer runs, when i change intgCONST3 to -8
Could there be a difference between the preprocessor/compiler and the avr computation ?
with -9 the remainder is ,86 with -8 its ,43?
Hmm, shouldn't be....
Anyone portet lwIP or uIP to FreeRTOS?

Have you tried the calculation without the scheduler running?

You could put a portENTER_CRITICAL()/portEXIT_CRITICAL() pair around the calculation. If the result is still the same then the scheduler is not interfering and it's something odd with the compilation.

Hello All;
I have some source code for Atmega128 and I want to port this source code into msp430f1611.
I would be very grateful if you could tell me what i have to consider so that the source could be run on it.
thanks

Do you mean you have FreeRTOS running on an ATMega128 and want the same app running under FreeRTOS on the MSP430? Or is this just a general question?

hello all
thank you for your reply
I mean a general question because i going to work on IAR compiler or msp430-gcc
thanks

Your question is too general to be able to offer a sensible answer - also this is a support forum for FreeRTOS and the question does not seem to relate to FreeRTOS.

Switching from one processor to another - is your code written in C or asm? The processor is different, the peripherals are different, the startup code will be different, your compiler will be different, the interrupt routines will be different, the pin usage will be different - what are you asking?

I am trying to run freeRTOS on the ATmega128 chip. I am using an ATmega128 Development Board from PRLLC (www.prllc.com). I have previous microcontroller experience with a Motorola 68HC11 chip and a PIC18LF448. However, this is my first time working with an RTOS and trying to port it to a chip.

I could use any help on setting up freeRTOS to run on this chip. I am using WinAVR v.20040404 for my development tools. I have perused the freeRTOS website, and should be able to find any reference made to it.

I have tried to make the demo program freeRTOS comes with using a make all command in Programmer's Notepad, which comes as part of the WinAVR environment. Everything compiles fine except I receive errors concerning undeclared variables in relation to serial.c

In conclusion, any help or pointing in the right direction would be much appreciated. Thank you for the time and help,

Josh Wittmier
Joshua.Wittmier@fluke.com

Hi Josh,

I have started a new thread for this, see the thread "Changes for ATMega128".

Regards.