Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training


LPC1768 Red Suite

Posted by alpha86 on April 4, 2012
Hi I have a RDB1768v2 board and I have followed the freeRTOS example at :

I first solved the ethernet issue due to the different component used in the demo for the RDB1768v1.

When I run the program from LPCxpresso, I get this at console, is that fine?:
set remotetimeout 60000
set mem inaccessible-by-default off
mon ondisconnect cont
set arm force-mode thumb

I will like to know what is the best way to get started. I am thinking of deleting all tasks from the example project mentioned above, and include the CMSIS folder (as with the official RDB1768v2 examples found on CodeRed website). However, I find that the core_cm3 file in the CodeRed examples(v2.1) are different from the one used in the freeRTOS demo (v1.3). Is it safe to just use the core_cm3 v2.1?

RE: LPC1768 Red Suite

Posted by MEdwards on April 4, 2012
set remotetimeout 60000
set mem inaccessible-by-default off
mon ondisconnect cont
set arm force-mode thumb

These are commands being sent by a script run in the IDE to GDB (the debugger). It is nothing to do with FreeRTOS and nothing to be concerned about as expected behavior.

I recommend always using the latest CMSIS files.

RE: LPC1768 Red Suite

Posted by alpha86 on April 9, 2012
Thanks edwards3, yup juz realized the gdb commands being sent.

Okay, I'll just use the latest CMSIS files then. Anyway, how can I know what is freeRTOS doing on the driver/interrupt/clock of the cortex-m3 and is the code written at this low level configuration compliant to CMSIS? I think my question is how can I see these codes and see if they reflect the new CMSIS and if not, I can change them. Is it recommended to touch these codes?

[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]

Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.

Free TCP/IP and file system demos for the RTOS

Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists