question about the version of the underlying MbedOS core

[jerabaul29]

This may be related to some previous questions, but I was curious of the following.

It looks like the underlying version of MbedOS core is quite old: https://github.com/sparkfun/mbed-os-ambiq-apollo3/tree/0773105959af71b6d21a6f722635d837b49ba344

If I am not confused, the latest updates coming from upstream MbedOS are from mid-2020: https://github.com/sparkfun/mbed-os-ambiq-apollo3/commits/0773105959af71b6d21a6f722635d837b49ba344?after=0773105959af71b6d21a6f722635d837b49ba344+69&branch=0773105959af71b6d21a6f722635d837b49ba344

Any reason for not upgrading the underlying MbedOS core? I suppose there have been quite many improvements and fixes in the last year?

[Wenn0101]

For a while this was due to ArduinoBLE compatibility.
Until the most recent release of ArduinoBLE in late February, it was only compatible with mbed 5, thus we did not upgrade because we were working on a very late version of Mbed5.
Looking at the latest release of this library it looks like we should be good to upgrade to Mbed6, but we have not quite gotten around to it yet. One of the items on my plate, fixing up floating point printf #278, may best be solved by upgrading to Mbed 6, so this update is probably not too far out.

[jerabaul29]

Would be exciting, would be great to benefit from MbedOS bugfixes and development.

[paulvha]

I think Serial communication is getting a bigger issue.

I was reading a great article about a big change in Mbed6 in the whole printf(): https://forums.mbed.com/t/hitchhikers-guide-to-printf-in-mbed-6/12492. Now it looks easy to just make the change in mbed_app.json.. however, this configuration file is NOT used when building a library, only when you compile a complete application. Also see #278

Next to that, it seems there is a difference in the way serial communication is handled between standard output and device serial. All explained in that article. I wonder about that impact.

regards,
Paul

[Wenn0101]

Closing this issue, as the question was answered. I will keep you all posted when large updates to the mbed core occur.