Upgrade ChanFs to R0.13a

[deepikabhavnani]

Upgrading ChanFS, follow link to know more about updates in ChanFS.

#4285

[0xc0170]

@deepikabhavnani Can you review jenkins failure. It indicates pal_plat_fileSystem.cpp@600,0: [Pe165]: too few arguments in function call . This is breaking PAL code?

Are any breaking changes expected with this update or should be backward compatible?

[deepikabhavnani]

PAL is using the ChanFs API (f_mkfs) directly instead of using FATFileSystem::format. It is breaking change from ChanFs, which is not backward compatible.
I am not sure why ChanFs API is used directly, it would be great if that is fixed in cloud client application. Else we can merge this commit in 5.7 release instead of patch.

[geky]

This looks great, thanks for putting this together 👍

[deepikabhavnani]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 536
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5490/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 152
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5490/

[0xc0170]

PAL is using the ChanFs API (f_mkfs) directly instead of using FATFileSystem::format. It is breaking change from ChanFs, which is not backward compatible.

👍

@avolinski @amiraloosh Can you please review the failures in the jenkins, as quoted above, PAL should use user facing API

[deepikabhavnani]

Rebased to resolve conflicts

[deepikabhavnani]

Fix in PAL: https://github.com/ARMmbed/mbed-client-pal/pull/331

[deepikabhavnani]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 567
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5490/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 180
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5490/

[mbed-ci]

Test : FAILURE

Build number : 382
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5490/382

[mbed-ci]

Test : SUCCESS

Build number : 385
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5490/385

[0xc0170]

@deepikabhavnani I restarted CI again. The last failure from yesterday indicates that the repo was not yet updated. I am failing to see at the moment the hierarchy, going to talk to pal team. Their pal client repo was updated, but not certain if this was also propagated to the client example that failed in the jenkins CI. I'll check

[0xc0170]

Update to the latest msg from me: I identified a failure in the logs, @JanneKiiskila and @teetak01 - need your assistance for jenkins CI failure here.

[deepikabhavnani]

#4285

[0xc0170]

All green ! @deepikabhavnani All ready? :)

[deepikabhavnani]

Yes.. ready to merge

[teetak01]

Verified that this fixes format-related issues present in Mbed OS 5.6.5 (and earlier) for Cloud Client.

[0xc0170]

@teetak01 👍 testing appreciated !