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] [April 2010 Threads] FreeRTOS on PIC32 Starter KitPosted by Hector on April 21, 2010 Hello,
I'm new with using RTOSes.
I need to implement a PIC32MX with FreeRTOS for our current project.
For the tests, all I have is a PIC32 Ethernet Starter Kit ( PIC32MX795F512L processor).
Since FreeRTOS comes with a demo project for the Explorer 16 developpement board with a plug in module (PIM) containing a PIC32MX360F512, could some one guide me on how to adapt the demo to the PIC32 Ethernet Starter Kit?
Thank you
RE: FreeRTOS on PIC32 Starter KitPosted by Dave on April 21, 2010 The PIC32 ebook comes with projects that run on the USB2 starter kit. I would suggest starting with those.
RE: FreeRTOS on PIC32 Starter KitPosted by Hector on April 21, 2010 Thank you for the information. For simple applications, it should make no difference which one on the Starter Kits I use.
RE: FreeRTOS on PIC32 Starter KitPosted by Dave on April 21, 2010 I was not suggesting you change starter kits. I was just suggesting you start with a project that is already configured to run on one of the new starter kits. The new PIC32 devices have at least one (maybe more?) extra configuration bits that must be set up for proper operation. If you start with a project that already has this configured you won't get any issues.
RE: FreeRTOS on PIC32 Starter KitPosted by Hector on April 27, 2010 Hello, I tried the RTOS demo on my PIC32 Ethernet Starter Kit. Most calls in the main.c are commented. I just keep: int main( void ) { prvSetupHardware();
vStartLEDFlashTasks( tskIDLE_PRIORITY );
vTaskStartScheduler();
return 0; }
I did the necessary changes in ParTest.c (PORTA becomes PORTD and the JTAG port is enabled so debugging is possible). When the program is running in "Animate" mode (automatic Step by step) the first LED (RD0, task priority of 0) does blink, but the program just keeps doing the "for(;;)" loop in flash.c No matter how long I wait, no other task stops this. Any ideas of what is the problem? Thank you
RE: FreeRTOS on PIC32 Starter KitPosted by Richard on April 27, 2010 What did you use as the starting point for the project? The code form the FreeRTOS download or the code that comes with the PIC32 book.
If the former, then did you add the extra
#pragma config FSRSSEL = PRIORITY_7
line?
Regards.
RE: FreeRTOS on PIC32 Starter KitPosted by Hector on April 28, 2010 Thnak you.
The three LEDs are now blinking.
I would like to understand why the line #pragma config FSRSSEL = PRIORITY_7 is necessary, tough.
RE: FreeRTOS on PIC32 Starter KitPosted by Richard on April 28, 2010 To quote a message from several days ago in this thread: “I was not suggesting you change starter kits. I was just suggesting you start with a project that is already configured to run on one of the new starter kits. The new PIC32 devices have at least one (maybe more?) extra configuration bits that must be set up for proper operation. If you start with a project that already has this configured you won't get any issues.”
RE: FreeRTOS on PIC32 Starter KitPosted by Hector on April 28, 2010 I see
Thank you for helping me
RE: FreeRTOS on PIC32 Starter KitPosted by WA4SWJ on April 22, 2011 Keydmer,
From the datasheet for the PIC32MX795 this command sets the interrupt priority for the shadow register. Sets bits 18-16 of the device configuration word 3.
Hope this helps.
Regards,
Ed Long
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|