Mbed-os: NU_PFM_M2351_NPSA_S: failing nightly in ATHandler - not supporting serial

[0xc0170]

Description of defect

NU_PFM_M2351_NPSA_S fails with an error:

Compile [  9.3%]: ATHandler.cpp
[Error] ATHandler.cpp@1548,17: unknown type name 'BufferedSerial'
[Error] ATHandler.cpp@1548,49: no member named 'set_baud' in 'mbed::FileHandle'
[ERROR] ./features/cellular/framework/device/ATHandler.cpp:1548:17: error: unknown type name 'BufferedSerial'
    static_cast<BufferedSerial *>(_fileHandle)->set_baud(baud_rate);
                ^
./features/cellular/framework/device/ATHandler.cpp:1548:49: error: no member named 'set_baud' in 'mbed::FileHandle'
    static_cast<BufferedSerial *>(_fileHandle)->set_baud(baud_rate);

The target has this in targets.json file:

        "device_has_remove": [
            "SERIAL",
            "SERIAL_ASYNCH",
            "SERIAL_FC",
            "STDIO_MESSAGES",
            "LPTICKER"
        ],

It does not support SERIAL, therefore the object BufferedSerial does not exists. A question is how ATHandler should handle this?

@ARMmbed/mbed-os-wan Please review

cc @ARMmbed/team-nuvoton

Target(s) affected by this defect ?

NU_PFM_M2351_NPSA_S

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

all

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

33563b3cfb

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

not relevant

How is this defect reproduced ?

Build the target (test or an example) and should fail

[ccli8]

This is re-raise of https://github.com/ARMmbed/mbed-os/pull/11594#issuecomment-544323169. Maybe follow the suggestion or exclude NU_PFM_M2351_NPSA_S from CI.

[kivaisan]

From ATHandler point of view, set_baud_rate can be ignored if serial is not supported, so it is easy to flag out.

[ciarmcom]

@0xc0170 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. '33563b3cfb' has not been matched as a valid tag or sha.
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.