Raspberry Pi Port - Almost Ready

James Walmsley

November 08, 2012 18:37

None

Hi Richard, and the FreeRTOS community,

I've managed to make a fully functioning port of FreeRTOS for the RaspberryPi. I shall post the full code here very shortly. I will also include a simple interrupt manager to handle the RaspberryPi interrupts, as this is really required to work correctly with FreeRTOS. Basically it has to determine which IRQ# is actually firing etc. (Kind of vectorising the interrupts for you).

In anycase, I saw in some older attempts to port to ARM11, in the portSAVE_CONTEXT() macro is a NOP. Does anyone know the real reason for this? I removed it from my code, and the Pi still runs perfectly. I suspect its some requirement for an older ARM core, or to aid debug stepping or something along those lines???

Also in an older ARM11 port they made some function calls in the ISR like: (I know this is a community port, so its not the usual high FreeRTOS standard).

__asm volatile ("bl vTaskIncrementTick");

Instead of:

vTaskIncrementTick();

I had some real problems because of this, there's no advantage to using the inline assembly, yet the compiler cannot know that the LR will be clobbered and therefore doesn't push it on function entry.

I suspect this is not a problem if the said function is the ISR called directly by the hardware, but if there's a callstack below it then there are problems.

Aside from that it wasn't too difficult. I just thought I'd mention this in case anyone searches for such a problem in the future.

I heard Rob Williams retired, its a bit of a shame that UWE isn't backing brilliant courses like CRTS anymore.

Take care,

James

save_context.txt

Date Votes

15 comments

0

James Walmsley November 11, 2012 19:32

Checkout a working snapshot from:

https://github.com/jameswalmsley/RaspberryPi-FreeRTOS

I'll add a proper README file in the coming days. On a Linux system it should build by typing make.

On windows, you'll need MSYS, Yagarto and Python to build.

James

Comment actions Permalink
0

Alberto Panu November 14, 2012 17:55

Hello James,

I've download the code and try compilation with ubuntu & gcc-arm-none-eabi-4_6-2012q4 but result in two errors:

Dark Builder - Unified Build Environment
Version (1.0.0 - Armstrong)
arm-none-eabi-ld: cannot find -lgcc
arm-none-eabi-ld: cannot find -lc
make: *** [kernel.elf] Errore 1

I never compile FreeRTOS and am a newbie, I must instal some dependencies?

Thanks

Alberto

Comment actions Permalink
0

James Walmsley November 14, 2012 18:05

Hi Alberto,

Firstly, thanks for taking the time to try it. It sounds like you are almost there!

The only problem is the library paths for libgcc and libc for the compiler.
You can edit these paths in the Makefile on lines 32 and 33.

Currently you will find the paths are pointing to a yagarto installation on Windows.

kernel.elf: LDFLAGS += -L"c:/yagarto/lib/gcc/arm-none-eabi/4.7.1/" -lgcc
kernel.elf: LDFLAGS += -L"c:/yagarto/arm-none-eabi/lib/" -lc

Note also the commented out lines for the Xilinx GCC compiler.

Hope that gets you up and running!

James

Comment actions Permalink
0

Alberto Panu November 15, 2012 09:57

Compiled with

kernel.elf: LDFLAGS += -L"/home/alberto/local/gcc-arm-none-eabi-4_6-2012q4/lib/gcc/arm-none-eabi/4.6.2/" -lgcc
kernel.elf: LDFLAGS += -L"/home/alberto/local/gcc-arm-none-eabi-4_6-2012q4/arm-none-eabi/lib/" -lc

now i should format a sd with fat and put in boot directory the kernel.img an fireup?

Comment actions Permalink
0

Dustin Sanders December 30, 2012 08:55

Hi guys!

James, thanks for taking the time to make this port! I'm having a helluva time compiling this in windows. I've got Yagarto 4.7.2 installed and I've updated the makefile with the correct directory. And the compiler was having problems with the .dbuild i had to remove the prevailing dot in order to make it semi-happy. I added paths to the include and lib files, which helped some errors i was getting, but can't seem to get rid of the size_t problem. Thanks!

Description Resource Path Location Type
Unused declaration of function 'xQueueAltGenericReceive' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 171 Code Analysis Problem
Unused declaration of function 'xQueueGetMutexHolder' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 180 Code Analysis Problem
Symbol 'size_t' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 340 Semantic Error
Unused declaration of function 'vApplicationTickHook' tasks.c /mppt_freertos_v0.1/FreeRTOS/Source line 315 Code Analysis Problem
Unused declaration of function 'vApplicationStackOverflowHook' tasks.c /mppt_freertos_v0.1/FreeRTOS/Source line 314 Code Analysis Problem
make: *** [kernel.elf] Error 1 mppt_freertos_v0.1 C/C++ Problem
Type 'size_t' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 325 Semantic Error
Unused declaration of function 'xQueueCreateMutex' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 166 Code Analysis Problem
Unused declaration of function 'xQueueTakeMutexRecursive' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 168 Code Analysis Problem
Unused declaration of function 'ucQueueGetQueueNumber' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 176 Code Analysis Problem
Unused declaration of function 'vQueueWaitForMessageRestricted' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 175 Code Analysis Problem
Type 'size_t' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 340 Semantic Error
Unused declaration of function 'xQueueCreateCountingSemaphore' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 167 Code Analysis Problem
Unused declaration of function 'xQueueAltGenericSend' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 170 Code Analysis Problem
Statement has no effect 'ulMaskedStatus + pRegs->Pending2' interrupts.c /mppt_freertos_v0.1/Demo/Drivers line 86 Code Analysis Problem
Unused declaration of function 'vQueueSetQueueNumber' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 177 Code Analysis Problem
Unused declaration of function 'xQueueGiveMutexRecursive' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 169 Code Analysis Problem
Unused declaration of function 'ucQueueGetQueueType' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 178 Code Analysis Problem
No return, in function returning non-void queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 961 Code Analysis Problem
No return, in function returning non-void queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 577 Code Analysis Problem Description Resource Path Location Type
Unused declaration of function 'xQueueAltGenericReceive' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 171 Code Analysis Problem
Unused declaration of function 'xQueueGetMutexHolder' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 180 Code Analysis Problem
Symbol 'size_t' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 340 Semantic Error
Symbol 'NULL' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 336 Semantic Error
Symbol 'NULL' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 326 Semantic Error
Type 'size_t' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 325 Semantic Error
Symbol 'NULL' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 1139 Semantic Error
Unused declaration of function 'xQueueCreateMutex' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 166 Code Analysis Problem
Unused declaration of function 'xQueueTakeMutexRecursive' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 168 Code Analysis Problem
Symbol 'NULL' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 933 Semantic Error
Symbol 'NULL' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 343 Semantic Error
Unused declaration of function 'ucQueueGetQueueNumber' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 176 Code Analysis Problem
Type 'size_t' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 340 Semantic Error
Unused declaration of function 'vQueueWaitForMessageRestricted' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 175 Code Analysis Problem
Unused declaration of function 'xQueueCreateCountingSemaphore' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 167 Code Analysis Problem
Unused declaration of function 'xQueueAltGenericSend' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 170 Code Analysis Problem
Unused declaration of function 'vQueueSetQueueNumber' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 177 Code Analysis Problem
Unused declaration of function 'xQueueGiveMutexRecursive' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 169 Code Analysis Problem
Symbol 'NULL' could not be resolved queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 1274 Semantic Error
Unused declaration of function 'ucQueueGetQueueType' queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 178 Code Analysis Problem
No return, in function returning non-void queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 961 Code Analysis Problem
No return, in function returning non-void queue.c /mppt_freertos_v0.1/FreeRTOS/Source line 577 Code Analysis Problem
Unused declaration of function 'vApplicationTickHook' tasks.c /mppt_freertos_v0.1/FreeRTOS/Source line 315 Code Analysis Problem
Unused declaration of function 'vApplicationStackOverflowHook' tasks.c /mppt_freertos_v0.1/FreeRTOS/Source line 314 Code Analysis Problem
make: *** [kernel.elf] Error 1 mppt_freertos_v0.1 C/C++ Problem
Statement has no effect 'ulMaskedStatus + pRegs->Pending2' interrupts.c /mppt_freertos_v0.1/Demo/Drivers line 86 Code Analysis Problem

Comment actions Permalink
0

Dustin Sanders December 30, 2012 09:05

Ok, So I missed an include path. But now it simply says: Error 1

Description Resource Path Location Type
make: *** [kernel.elf] Error 1 mppt_freertos_v0.1 C/C++ Problem

Also Line: 86 in interrupts.c there was an error:

ulMaskedStatus + pRegs->Pending2;

replaced with:

ulMaskedStatus = pRegs->Pending2;

Comment actions Permalink
0

Dustin Sanders December 30, 2012 09:12

I sure wish i could edit previous posts..

There seems to be a lot of missing Implementations of function prototypes, I tried to find where vApplicationTickHook and vApplicationStackOverflowHook but haven't been successful. How as everyone else been able to compile this?

Comment actions Permalink
0

Dustin Sanders December 30, 2012 11:40

So I decided to see what luck I would have with Linux, fresh install of latest ubuntu with build-essiental and gcc-arm packages. I get:

$ make
Dark Builder - Unified Build Environment
Version (1.0.0 - Armstrong)
: No such file or directory
make: *** [/media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/portable/GCC/RaspberryPi/port.o] Error 127

I looked at the build files and was playing around with how port.c includes the interrupt driver, but everything i tried was futile. Could it be the toolchain? I know windows with yagarto its arm-none-eabi- but in linux it appears to be arm-linux-gnueabi-.

If i only it would tell me WHAT file it was looking for, the blank and lack of line number is a pretty aggravating error.

If anyone has thoughts to all of the above it would be greatly appreciated.

Comment actions Permalink
0

James Walmsley December 30, 2012 12:50

Hi Dustin,

Thanks for trying this :D I guess your using some source code analysis checker, which I didn't use, so a lot of errors seem to come from this.

>> There seems to be a lot of missing Implementations of function prototypes, I tried to find where vApplicationTickHook and vApplicationStackOverflowHook but haven't been successful. How as everyone

>> else been able to compile this?

I think these are usually defined to nothing if they are unused.

You can also run make with V=2 or V=3, this will give you more information as you'll see the command that make actually calls.

$ make V=2

I'll have a closer look at your other errors to see if I can work out whats going on.

Did you get the code from https://github.com/jameswalmsley/RaspberryPi-FreeRTOS ?

I have this working on yagarto in Windows (I used MSYS, but I also had to have a working python in my path).

On Linux it also works, but I use the codesourcery toolchain.

Let me know what the failing command is with V=2.

James

Comment actions Permalink
0

Dustin Sanders December 30, 2012 17:42

James,

Thanks for the suggestions. It was the toolchain, i switched to arm-linux-gnueabi and it started to compile however still having issues with the dbuild

$ make V=2
Dark Builder - Unified Build Environment
Version (1.0.0 - Armstrong)
arm-none-eabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/ /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/port.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/portable/GCC/RaspberryPi/port.o
make: arm-none-eabi-gcc: Command not found
make: *** [/media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/portable/GCC/RaspberryPi/port.o] Error 127

make V=2
Dark Builder - Unified Build Environment
Version (1.0.0 - Armstrong)
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/ /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/port.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/portable/GCC/RaspberryPi/port.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/portisr.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/portable/GCC/RaspberryPi/portisr.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/croutine.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/croutine.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/list.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/list.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/queue.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/queue.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/tasks.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/FreeRTOS/Source/tasks.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/interrupts.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/Demo/Drivers/interrupts.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/gpio.c -o /media/sf_Code/mppt_RPi_FreeRtos/build/Demo/Drivers/gpio.o
arm-linux-gnueabi-gcc -MD -MP -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -march=armv6z -g -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/portable/GCC/RaspberryPi/ -I /media/sf_Code/mppt_RPi_FreeRtos/FreeRTOS/Source/include/ -I /media/sf_Code/mppt_RPi_FreeRtos/Demo/Drivers/ -c /media/sf_Code/mppt_RPi_FreeRtos//FreeRTOS/Source/portable/MemMang/heap_4.c -o /media/sf_Code/mppt_RPi_FreeRtos/build//FreeRTOS/Source/portable/MemMang/heap_4.o
/media/sf_Code/mppt_RPi_FreeRtos/.dbuild/pretty/pretty.py --dbuild "AS" "RaspberryPi BSP" startup.o
: No such file or directory
make: *** [/media/sf_Code/mppt_RPi_FreeRtos/build/Demo/startup.o] Error 127

Or it has something to do with the startup file, I'll keep investigating.

Comment actions Permalink
0

James Walmsley December 30, 2012 18:52

Hi Dustin,

Thanks for perservering with this one. In the .dbuild directory ensure that all python files are marked executable.

$ cd .dbuild/pretty/

$ chmod +x *.py

Also just looking at the pretty.py script the first line:

#!/usr/bin/env python

Try changing it to:

#!/usr/bin/python

Or wherever your python is.

James

Comment actions Permalink
0

James Walmsley December 30, 2012 19:08

Also you could change it to:

#!/bin/which python

I mainly develop on Ubuntu based machines, and I found that /usr/bin/env was available under msys and Ubuntu which is why I used that. I think /bin/which is more "portable" though.

p.s. You can Skype me on james.walmsley if you like, we might get the job done a bit quicker.

James

Comment actions Permalink
0

Dustin Sanders January 04, 2013 04:41

So I've been playing with it a bit. I'm making strides. I decided to start over and download a fresh copy of your code. I updated it with arm-linux-gnueabi and the location of the libraries. I get all the way to linking and now i have this:

$ make V=2
Dark Builder - Unified Build Environment
Version (1.0.0 - Armstrong)
arm-linux-gnueabi-ld /media/sf_Code/RaspberryPi-FreeRTOS-master/build/FreeRTOS/Source/portable/GCC/RaspberryPi/port.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/FreeRTOS/Source/portable/GCC/RaspberryPi/portisr.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/FreeRTOS/Source/croutine.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/FreeRTOS/Source/list.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/FreeRTOS/Source/queue.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/FreeRTOS/Source/tasks.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/Demo/Drivers/interrupts.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/Demo/Drivers/gpio.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build//FreeRTOS/Source/portable/MemMang/heap_4.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/Demo/startup.o /media/sf_Code/RaspberryPi-FreeRTOS-master/build/Demo/main.o -Map kernel.map -o kernel.elf -T raspberrypi.ld -L"/usr/lib/gcc/arm-linux-gnueabi/4.7" -lgcc -L"/usr/arm-linux-gnueabi/lib/" -lc
arm-linux-gnueabi-ld: error: required section '.rel.plt' not found in the linker script
arm-linux-gnueabi-ld: final link failed: Invalid operation
make: *** [kernel.elf] Error 1

I'm searching messing with it. If anyone's run into this error i'd love to see how it was fixed.

Comment actions Permalink
0

Dustin Sanders January 04, 2013 06:37

Update!

So I suspected the fact that i was using the arm-linux-gnueabi and not arm-none-eabi which might be the issue.

I went to:

https://launchpad.net/gcc-arm-embedded

and download that guy, then compiled just fine. I still need to see if I can get it working under windows. Thanks for your help!

Comment actions Permalink
0

raspPipt April 29, 2013 10:17

Hi all,

I'm using the GPIO interrupt but I have a problem. When an interrupt occurs, function vFreeRTOS_ISR(void) is called, that should save context, call irq_handler() and restore context.

What I see is that the callback associated to the GPIO interrupt is called, but the program execution seems not to return to the main function.

Has anyone noticed a similar problem?
Many thanks.

Comment actions Permalink

Please sign in to leave a comment.