[RTOS Support] LPC23xx

Quality RTOS & Embedded Software

About Contact Support FAQ Download

Menu

Quick Start

Supported MCUs

PDF Books

Trace Tools

Ecosystem

Quick Start Guide

Support Forum

⇓ Download Source ⇓

FreeRTOS+ Ecosystem

FreeRTOS+TCP:
Thread safe TCP/IP stack

SafeRTOS:
TUV certified RTOS

OpenRTOS:
Commercial Licensed RTOS

Fail Safe File System:
Ensures data integrity

FreeRTOS BSPs:
3rd party driver packages

Trace & Visualisation:
Tracealyzer for FreeRTOS

CLI:
Command line interface

WolfSSL SSL / TLS:
Networking security protocols

RTOS Training:
Delivered online or on-site

IO:
read(), write(), ioctl() interface

FreeRTOS+ Lab Projects

FreeRTOS+POSIX:
POSIX threading API

FreeRTOS+FAT:
Thread aware file system

FreeRTOS Support Archive

The FreeRTOS support forum is used to obtain active support directly from Real Time Engineers Ltd. In return for using our top quality software and services for free, we request you play fair and do your bit to help others too! Sign up to receive notifications of new support topics then help where you can.

This is a read only archive of threads posted to the FreeRTOS support forum. The archive is updated every week, so will not always contain the very latest posts. Use these archive pages to search previous posts. Use the Live FreeRTOS Forum link to reply to a post, or start a new support thread.

[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [November 2012 Threads]

LPC23xx

Posted by OXO on November 19, 2012

I'm just starting a new project with freertos on LPC2387, Code Red tools. I've used their wizard to make a new shell freertos project.

It builds and loads fine, but vectors to program abort

LDR pc,_pabt // program abort

when portRESTORE_CONTEXT()

in

vPortISRStartFirstTask() is called.

It's using freertos v 7.0.1

RE: LPC23xx

Posted by Richard on November 19, 2012

As your project was created by somebody else's tool I can't support it directly, but suspect your problem will be that the MCU is in the wrong mode. Make sure the MCU is in Supervisor mode when main() is called.

Regards.

RE: LPC23xx

Posted by OXO on November 19, 2012

Thanks for the fast reply Richard, but I've already tried that.

main is called:-


        LDR   r3, .def__main
        CMP   r3, #0
        BEQ   .newlib_main
        LDR   r10,=__main
        B     .call_app
.newlib_main:
        LDR   r10,=main
.call_app:

// Change to user mode (interrupts enabled) before calling main application
        //MSR   CPSR_c,#MODE_USR

        // change to Supervisor mode
        msr   CPSR_c, #MODE_SVC|I_BIT|F_BIT

        MOV   lr,pc
        BX    r10                       // enter main() - could be ARM or Thumb

RE: LPC23xx

Posted by OXO on November 21, 2012

So, I am over that problem, but now I have that the ticks are not being incremented. Where are the interrupts re-enabled after the disable in vTaskStartScheduler?

Is it the portRESTORE_CONTEXT in vPortISRStartFirstTask?

RE: LPC23xx

Posted by Dave on November 21, 2012

All the ports disable interrupts before starting the scheduler, then automatically enable them as the context of the first task to run is restored.

RE: LPC23xx

Posted by OXO on November 21, 2012

This is frustrating. ;) .. as always in embedded ...

So the code is running, and I can break in and it's in the idle task. looks good.

But the xTickCount is not incrementing. So, check the timer setup. That's correct and the TCR is changing.

VICIrqStatus is 0x10, which means that the interrupt is triggered but not serviced.

cpsr is 0x6000001f, which I interpret to mean that the interrupts are enabled.

So what could be wrong??

RE: LPC23xx

Posted by Richard on November 21, 2012

If interrupts are not disabled, then it sounds like the tick interrupt is simply not executing for some reason. Put a break point in the vPreemptiveTick() function (portISR.c). If it never gets hit, but other interrupts are executing, then check the function vPreemptiveTick() (port.c) is correct for your derivative of the chip.

Regards.