I had a quick look, card is still identified as VRBrain in the driver’s list. Trying to update the firmware with Mission Planner doesn’t look OK. I think we have to stay with the custom .apj upload.
Marc
I am still confused (not hard).
So we use the .apj file as custom firmware through MP. Is that all we have to do? Does this mean that ChiBios Ardupilot is running on VR boards now? I thought that Nuttx was deprecated so if this is the latest Dev branch than it must be ChiBios — or am I just misguided.
I never saw any announcement so has Luca been working on this?
There were some hints in the GitHub ardupilot code section.
https://github.com/ArduPilot/ardupilot/commit/e15d2c0f891b5ab6665acfcc71fec57a0f57086b
Now it is alive,
Marc
Eagle eyes!
Has anyone tested this do you know?