Mbed-os: mbed_drivers-buffered_serial Test fails for SDP-K1

[malavikasajikumar]

Description of defect

mbed-os-tests-mbed_drivers-buffered_serial test fails on SDP-K1 for the master branch mbed-os. Recent modifications were made to the STM_32 Family definition. Before these edits, this test was not run for SDP-K1.
The error says "SYNC FAILED".

Target(s) affected by this defect ?

SDP-K1 uses STM32F469NI

Toolchain(s) (name and version) displaying this defect ?

GCC_ARM

What version of Mbed-os are you using (tag or sha) ?

https://github.com/ARMmbed/mbed-os/commit/6c9d16843cf0fc97aa50b438ac99fcc258ec4d67

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

mbed-cli --version
1.10.4

How is this defect reproduced ?

1. mbed new mbed_test_master
2. Git switch branch to master on mbed-os
3. mbed test -t GCC_ARM -m SDP_K1 -n mbed-os-tests-mbed_drivers-buffered_serial -v

SDP_K1_GCC_ARM_master_serial_test.log

[ciarmcom]

@malavikasajikumar thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .
E.g. 'mbed-os-99.99.99' signifies master branch and is not a unique single snapshot.
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[0xc0170]

mbed-os-tests-mbed_drivers-buffered_serial test fails on SDP-K1 for the master branch mbed-os. Recent modifications were made to the STM_32 Family definition. Before these edits, this test was not run for SDP-K1.

Means the bug has been there for longer, correct?

cc @ARMmbed/team-st-mcd

[0xc0170]

mbed-os-tests-mbed_drivers-buffered_serial test fails on SDP-K1 for the master branch mbed-os. Recent modifications were made to the STM_32 Family definition. Before these edits, this test was not run for SDP-K1.
The error says "SYNC FAILED".

One more question, what is the last revision (SHA) that worked?

[ciarmcom]

@malavikasajikumar it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@malavikasajikumar it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[malavikasajikumar]

mbed-os-tests-mbed_drivers-buffered_serial test fails on SDP-K1 for the master branch mbed-os. Recent modifications were made to the STM_32 Family definition. Before these edits, this test was not run for SDP-K1.
The error says "SYNC FAILED".

One more question, what is the last revision (SHA) that worked?

SHA-1: b6370b4c37f3d4665ed1cdcb1afea85396bba1b3

[malavikasajikumar]

mbed-os-tests-mbed_drivers-buffered_serial test fails on SDP-K1 for the master branch mbed-os. Recent modifications were made to the STM_32 Family definition. Before these edits, this test was not run for SDP-K1.

Means the bug has been there for longer, correct?

cc @ARMmbed/team-st-mcd

@0xc0170 Not sure if this bug was there for longer, but with the "latest" tagged mbed-os, mbed-os-tests-mbed_drivers-buffered_serial test gets skipped for SDP-K1. For the master branch, it biulds and tried to run the test, and reports a SYNC_FAILED.

Also, the FAMILY_STM32 definition was modified on targets.json recently, and corresponding changes were made to the SDP-K1 portion. These changes were not from ADI. How can we make sure the ADI team is notified from the Mbed side of any such changes in the future. We are working with @jeromecoutant to make sure any changes are tested on SDP-K1 as well. However, what is Mbed's policy of informing Board vendors when board support package of its Target vendor gets modified? @andypowers

[ciarmcom]

@malavikasajikumar it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[malavikasajikumar]

@malavikasajikumar it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

Hello, this has been fixed. Please confirm.

[malavikasajikumar]

@0xc0170 @jamesbeyond We have a few modifications to make to the SDP-K1 board support package that are stable on the "latest" tag mbed-os. How should we submit the changes? Does it still make sense to submit the changes to master branch where one of the tests fail?

[ciarmcom]

@malavikasajikumar it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[malavikasajikumar]

https://github.com/ARMmbed/mbed-os/issues/13157
Answered here.

[0xc0170]

👍 if any further question, just ask in the 13157 issue