LoRaWAN: Memory overrun correction

[hasnainvirk]

Description

A typo in LoRaPHYCN470 is causing memory overrun.
We were supposed to fill-in default channel mask and iterate over CN470_CHANNEL_MASK_SIZE times.

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change

[hasnainvirk]

@0xc0170 @kjbracey-arm Please review. This needs immediate CI and merge.

[hasnainvirk]

@0xc0170 @cmonr This one is still lingering here ?

[kjbracey]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : FAILURE

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

[hasnainvirk]

@cmonr @0xc0170 The failure is not related to this PR. Please re-run CI.

[mbed-ci]

Test : FAILURE

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

[cmonr]

@hasnainvirk Will restart both export and test CI in a bit. Current queues a bit long.

[hasnainvirk]

@cmonr Have we missed this again ?? This is a broken , we must get this PR in as fast as we can. It's been about 8 days now, this PR is just a one liner !

[cmonr]

@hasnainvirk We missed this because we've been prioritizing PRs needed for 5.10 RCs.

/morph test
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : SUCCESS

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

[kivaisan]

@cmonr Could you please reconsider this to be part of 5.10.0? This is a quite bad memory corruption bug.

[hasnainvirk]

@cmonr This must go in as soon as possible. Please prioritise.

[adbridge]

@ChiefBureaucraticOfficer Could you please let us know if you think this should come in to 5.10 as requested by @hasnainvirk . AFAIK it has not been seen in OOB so would technically not normally be considered.

[0xc0170]

If this is not critical/blocker, this will go 5.10.1. This is now going in, the label can be updated on request.