FreeRTOS on BeagleV Fire

BeagleV
1

Just wanted to ask if anyone has managed to get the bare metal example mpfs-uart-mac-freertos_lwip working on the BeagleV Fire.
I have configured the board using mpfs-hal-ddr-demo and loaded the FreeRTOS application using ymodem as described in the readme and that all appears ok.
When I start the FreeRTOS application it does not work and exhibits random behavior. Attaching the debugger hasn’t been much help, sometimes it’s in handle_local_beu_interrupt function, other times it appears to stuck at startup in init_memory().
It feels like a memory corruption issues but looking to see if anyone else has suceeded.
Thanks, Nigel.

2

hi Nigel,
The stage that you got to is quite interesting to me, and although I would not be able to help much with this, what you have done already is interesting and hopefully soon a way to run freertos properly is found and documented,
Cheers,
martin

3

Have you properly configured the target hardware by defining the TARGET_BEAGLEV_FIRE macro in the project config? The default build is for the Icicle Kit and you have to properly select the BeagleV to get the right board config etc.

Regards,
Peter

4

Hi Peter,
I have selected the DDR-Release-BeagleV-Fire build configuration which defines TARGET_BEAGLEV_FIRE so I think I have that covered.

I am using the mpfs-hal-ddr-demo as my bootloader and using this I can successfully load and run the mpfs-hal-run-from-ddr-u54-1-u54-2 example so my workflow seems to be ok using this simple example, but when trying mpfs-uart-mac-freertos_lwip it disappears into the weeds shortly after bootloader handover in the loaded program startup code.

I am assuming this example worked when first released on the icicle kit but not sure what is happening with current version on the BeagleVFire so wondering if it works for anyone else. I did see one issue report on the bare metal examples github but can’t tell if this is the same problem.

I have experience in embedded development but am new to PolarFire/Risc-V/FreeRTOS so it’s a bit of a steep learning curve.

Thanks for your input, Nigel.

1 Like