search

ARMmbed / mbed-os

Arm Mbed OS is a platform operating system designed for the internet of things
https://mbed.com
Other
4.67k stars 2.98k forks source link

Unable to configure SW2 (P0_4) as input on CY8CPROTO_062_4343W #11762

Closed linlingao closed 3 years ago

linlingao commented 4 years ago

Description of defect

I'm trying to configure the user button (SW2) on the Cypress Proto board as a Pelion device management resource. I found that this pin (Port 0 Pin 4) was also used as a WiFi host wakeup source. So I ran Device Configurator and switched to Pin 0_3 as a WiFi host wakeup source. I verified via debugger Pin 0_3 was indeed used as the wakeup source. However, I'm still seeing a pulse on P0_4 at 300ms to 700ms interval. I didn't find the code that drives this pin. Capture

Target(s) affected by this defect ?

CY8CPROTO_062_4343W

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

GCC_ARM

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

679d24833acf0a0b5b0d528576bb37c70863bc4e

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

N/A

How is this defect reproduced ?

Will need to regenerate BSP code to use P0_3 as wakeup source. Then build and run mbed-os-example-pelion.

linlingao commented 4 years ago

@maclobdell @ARMmbed/team-cypress

ciarmcom commented 4 years ago

@linlingao 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. 'https://github.com/ARMmbed/mbed-os/#679d24833acf0a0b5b0d528576bb37c70863bc4e' 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.

ciarmcom commented 4 years ago

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2466

ciarmcom commented 3 years ago

We closed this issue because it has been inactive for quite some time and we believe it to be low priority. If you think that the priority should be higher, then please reopen with your justification for increasing the priority.