FREERTOS and multicore usage (Sensors)

[weezybot]

So I’m currently trying to use FreeRTOS to place sensors in the background of a project on core 1 and motors on the primary core. I’ve used the SDK Examples one for the primary (master / motors) and one for the slave (secondary core / sensors). I’ve been able to generate the ping example however once I attempt to integrate my sensor data to be sent as packets (an ultrasonic) I have trouble even receiving the data, as it seems the echo rise never gets seen. I’ve configured my trig and echo in the pin mux. And have tried various things however I am still not getting sensor data correctly. What should I try or what am I doing wrong. 

[luis_maravilla]

Hello,

Could you help us bring the following details:

What MCU/Board are you using?

Which SDK version and examples are you using?

Could you share your pin mux configuration?

Which is the priority for the sensor task?

Are you using interrupts?

Any more information about your configuration is highly appreciated

Probably this link is helpful for your project

This link implements an Ultrasonic sensor with a Kinetis FRDM board.

Tutorial: Ultrasonic Ranging with the Freedom Board | MCU on Eclipse

Best Regards, Luis

[weezybot]

We are using the FRDMCXN947 and the SDK examples we are using are the frdm_freertos_message_buffers_primary_core, which will be used for motors and receiving the sensor data (messages) and frdm_freertos_message_buffers_secondary_core which is where the sensors will function and send their data. i currently have time of flights and ultrasonics and an imu however am implementing the ultrasonic sensor first. when i run the SDK examples with my sensor code. 

It is the only active application task on the secondary core, so there is no contention with other tasks at this time. The task periodically performs a blocking ultrasonic measurement and then sends the result to Core 0 using a FreeRTOS message buffer, followed by a delay (vTaskDelay) to control the update rate (~1 Hz during testing).

We are not using any additional higher-priority tasks on Core 1 at the moment. At this stage, we intentionally kept the task simple and isolated on Core 1 to validate sensor functionality before introducing additional tasks or prioritization.