[RTOS Support] error compilation with dspic33F

The FreeRTOS kernel is now an MIT licensed AWS open source project, and these pages are being updated accordingly.

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] [August 2010 Threads]

error compilation with dspic33F

Posted by john264 on August 30, 2010

when i compile my project i have this warning:

warning: passing argument 1 of 'xTaskGenericCreate' from incompatible pointer type

does someone has got already this warning. i think it is a bug with compiler C30 on
MPLAB. Does someone can help me?
Best regards

RE: error compilation with dspic33F

Posted by Dave on August 30, 2010

The first parameter is a function pointer, what is the prototype of the function being pointed to?

RE: error compilation with dspic33F

Posted by Richard Damon on August 30, 2010

The task function passed as the first parameter MUST be defined as "void fun(void *arg)" or you will get an error/warning.If the task wants the argument to be of a different type, it should change it inside the function. Using a different type of pointer may "work" as all pointers "look" the same on most machines now a days (including the dspic series), but it is a violation of the C standard as it is NOT true for all machines. in particular, machines which use "word" addressing instead of byte addressing.