STM32L4: before calling HAL_CRYP_DeInit initialize the Instance member

[juhoeskeli]

Description

Tested with wise 1570 (STM32L4) & cloud client. When function aes_set_key is called the function HAL_CRYP_DeInit calls macro __HAL_CRYP_DISABLE which dereferences null pointer (Instance). The target ends up HardFaulting. The issue was uncovered by the MPU overhaul change which was recently introduced.

To fix this, the Instance member should be initialized before calling HAL_CRYP_DeInit. This fixes the issue for workaround #8922.

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

[juhoeskeli]

@0xc0170 please take a look

[0xc0170]

@ARMmbed/team-st-mcd we would like to take this to the 5.11-rc2 (labeled as such), can you please review ?

[0xc0170]

Tested with wise 1570 (STM32L4) & cloud client. When function aes_set_key is called the function HAL_CRYP_DeInit calls macro __HAL_CRYP_DISABLE which dereferences null pointer (Instance). The target ends up HardFaulting. The issue was uncovered by the MPU overhaul change which was recently introduced.

Nice catch

[0xc0170]

Travis failure will be fixed on master soon (we will request rebase once done). See #8945

[0xc0170]

Travis failure will be fixed on master soon (we will request rebase once done). See #8945

The fix is on master, if you rebase, it should allow travis to run

[juhoeskeli]

Done rebasing

[cmonr]

CI started

[mbed-ci]

Test run: SUCCESS

Summary: 4 of 4 test jobs passed
Build number : 1
Build artifacts
Build logs