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




Loading

PIC demo port, problem with symbols

Posted by Brian Carver on October 17, 2009
I have been working on porting the example demo application from the Explorer 16 development board to the Explorer 16 starter kit. So far I have isolated all the needed bits, and changed to the main loop to a simple LET strobe program. I had followed the instructions on the freeRTOS website on ports.

So far so good, but I am having a major problem with the processor symbols.

> Make: The target "C:\Documents and
> Settings\Owner.bclaptop\My
> Documents\ovation\Common\Minimal\crflash.o"
> is up to date. Make: The target
> "C:\Documents and
> Settings\Owner.bclaptop\My
> Documents\ovation\PIC24_MPLAB\ParTest\ParTest.o"
> is out of date. Executing:
> "C:\Microchip Starter Kits\PIC24F
> Starter Kit 1\MPLAB
> C30\bin\pic30-gcc.exe"
> -mcpu=24FJ256GB106 -x c -c "ParTest.c" -o"ParTest.o" -I"."
> -I".\include" -I"..\include" -I"..\..\include" -I"..\..\..\include" -I"..\Source\include" -I"..\..\Source\include" -I"..\..\..\Source\include" -I"..\PIC24_MPLAB" -I"..\..\PIC24_MPLAB" -I"..\..\..\PIC24_MPLAB" -I"..\..\..\..\PIC24_MPLAB" -I".\FileSystem" -I"..\Common\include" -I"..\..\Common\include" -D__DEBUG -fno-omit-frame-pointer -g -Wall -DMPLAB_PIC24_PORT -mlarge-code -O1 -fno-schedule-insns -fno-schedule-insns2 ParTest.c: In function 'vParTestInitialise':
> ParTest.c:65: error: 'TRISA'
> undeclared (first use in this
> function) ParTest.c:65: error: (Each
> undeclared identifier is reported only
> once ParTest.c:65: error: for each
> function it appears in.) ParTest.c:66:
> error: 'PORTA' undeclared (first use
> in this function) ParTest.c: In
> function 'vParTestSetLED':
> ParTest.c:82: error: 'PORTA'
> undeclared (first use in this
> function) ParTest.c: In function
> 'vParTestToggleLED': ParTest.c:107:
> error: 'PORTA' undeclared (first use
> in this function) Halting build on
> first failure as requested.
> ---------------------------------------------------------------------- Debug build of project `C:\Documents
> and Settings\Owner.bclaptop\My
> Documents\ovation\PIC24_MPLAB\RTOSDemo_PIC24.mcp'
> failed. Preprocessor symbol `__DEBUG'
> is defined. Target debug platform is
> `__MPLAB_DEBUGGER_SKDE=1'. Debug
> platform options are: `__ICD2RAM=1'.
> Fri Oct 16 10:44:35 2009

I changed the linker script from the p24FJ128GA010.gld script to the p24HJ256GP210.gld as the PIC24FJ256GB106 chip is on the starter board.

So here is my problem, ( I am sure it will not be my last problem :-) ): I can not figure out how to get the development environment to understand where to find the symbols using the new script. So this is really an IDE/compiler problem.

Thanks in advance!

RE: PIC demo port, problem with symbols

Posted by Brian Carver on October 18, 2009
I figured it out. The switch in chip went with one with a portA to one without portA it starts with portB.

RE: PIC demo port, problem with symbols

Posted by Mike Hibbett on October 18, 2009
Yes, that one get's me every time too!

By the way, did you also change the CPU type in the MPLAB IDE?
(that Configure->Select Device from the main menu )

Mike.

RE: PIC demo port, problem with symbols

Posted by Brian Carver on October 19, 2009
I did make the change. The compiler complains about that one early on. The big lesson I learned in digging back into PIC is the "upgrade and multi-function" quality really understand the details.

For example the linker script will define the symbols but the linker script represents more processors. Also The datasheet is misleading because they discuss on the features until you look on the chart showing is there. So my fix is to pull up the 'h' file for the SPECIFIC processor and dig through that before I pick something.


[ 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