FlashIAP::program failed on ODIN board

[Alonof]

Description

• Type: Bug
• Priority: Major

Bug

Target
UBLOX_EVK_ODIN_W2

Toolchain:
GCC_ARM|ARM|IAR

Toolchain version:

mbed-cli version:
1.2.0

Expected behavior
FlashIAP:: program failed programming the internal flash on Odin Board.
Same code that runs on NUCLEO F429ZI ( the same CPU has ODIN) passes while in ODIN is failing

Actual behavior
calling FlashIAP:: program on ODIN

Steps to reproduce

[0xc0170]

cc @andreaslarssonublox @andreaspeterssonublox

[andreaslarssonublox]

Hi @Alonof,
We have tested it for the latest driver release candidate here #5287 and also for the previous #4567 and the FlashIAP test cases passed.

Can you provide the following:

• test application
• mbed-os commit SHA
• toolchain versions

[0xc0170]

@Alonof bump

[Alonof]

after running the tests today
there is no failure on the flash API

[Alonof]

reproduce steps

deploy and compile PAL
https://github.com/ARMmbed/pal-example

Run PAL example bin
Flash is failing with the following errors:

Programming alignment error
Programming parallelism error

[Alonof]

https://jira.arm.com/browse/IOTPART-3659

[0xc0170]

@Alonof The repository is private, can you share public one to be able to test it?

Looking at the errors, they both come from ST HAL, wrong usage of their driver? the flash implementation is shared for all STM32F4 targets

[Alonof]

Hi @0xc0170 I See you have permission for PAL repository
These errors come from the H/W,
The same code is running on NUCLEO and ODIN boards but only on ODIN it fails

[0xc0170]

Hi @0xc0170 I See you have permission for PAL repository

It was not about me, but a bug report should have all available information publicly accessible.
As @andreaslarssonublox requested above #5281 (comment) , to be able to reproduce them, they will need those information.

FlashIAP:: program failed programming the internal flash on Odin Board.

What is the exact failure, error return code? Any debug info ? Call stack?

Tests might be passing but app failing (I would like to find out if we are missing test coverage or where is this bug coming from).

Update:

Latest master (SHA 3c793a714 - (HEAD -> master, upstream/master) Merge pull request #5087 from mprse/rtc_test)

+---------------------------+-------------------+-----------------------------+---------------------------+--------+--------+--------+--------------------+
| target                    | platform_name     | test suite                  | test case                 | passed | failed | result | elapsed_time (sec) |
+---------------------------+-------------------+-----------------------------+---------------------------+--------+--------+--------+--------------------+
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-mbed_drivers-flashiap | FlashIAP - init           | 1      | 0
    | OK     | 0.05               |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-mbed_drivers-flashiap | FlashIAP - program        | 1      | 0
    | OK     | 4.71               |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-mbed_drivers-flashiap | FlashIAP - program errors | 1      | 0
    | OK     | 0.05               |
+---------------------------+-------------------+-----------------------------+---------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 3 OK
mbedgt: completed in 21.76 sec

[Alonof]

Hi
The errors come from the flash register.
here are the errors:

1. Programming alignment error
2. Programming parallelism error

Error 1 - the driver should handle the writing.
Error 2 - Also the driver should handle parallelism flow, also the flash APIs are blocking

When running PAL flow the flash is failing with the above erros

[0xc0170]

For those 2, what are the input parameters (address, sizes of data - to know if multiple banks are involved), if we can reproduce the arguments in our test, or at least small code snippet.

@andreaslarssonublox Do you recognize those errors and suspect what can cause them?

[andreaslarssonublox]

No, I don't recognize the errors and need the test application to be able to reproduce it. If this can't be shared publicly you can send it to my e-mail instead.