Hi All, With 4.6.0 and this particular type of FC, I found that MAVftp doesn’t work as I can’t create a scripts directory(since AP doesn’t make it automatically when I did SCR_ENABLE) or upload something. I switched back to 4.5.7, which has no problem to do so. I don’t expect many work on JFB110 but wanted to report. kozmi
1 Like
Hi @kozmi,
Thanks for the report I’ve added it to the 4.6 issues list.
No pressure of course, but please consider helping us with beta testing in the future so we can catch these problems before the stable release. Txs again for the report though in any case.
Hi rmackay, Sure. No pressure my pleasure. It’s good to hear from you.
Hi @kozmi,
In my testing the JFB110 board doesn’t seem to boot correctly at all. It also seems like Mission Planner isn’t correctly identifying the board which leads to the user having to scroll down through the list of available firmwares.
Can I ask how you built and/or uploaded the firmware?
OK, I’ve found that this PR is the cause of the problems. If we revert this then the JFB110 boots normally. Now that we’ve found the cause, it shouldn’t be too hard to resolve it.
It’s slightly worrying that this issue went unnoticed for over a year. To me this means that nobody is testing the board during betas let alone with “latest”. Either that or they’re not reporting issues. If you have any ideas about improving beta testing that would be greatly appreciated.
I’ve also raised a Mission Planner issue to resolve the board not being recognised
Hi rmackay,
In my case I didn’t notice an issue in terms of booting with 4.5 or 3.something that was preinstalled. MP’s updater worked. Yes it was worrisome if even manufacturer hadn’t looked.
kozmi
OK, JAE has kindly provided a fix which is included in this PR