You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can not use DigitalIn, InterruptIn, AnalogIn APIs while programming the Artemis Thing Plus. Mbed Studio tells these are unknown type names. My question is: is this a bug or are these API still unimplemented for the Apollo3 MCU? If so, is there an estimated time when these get implemented?
EDIT:
After restarting my computer only AnalogIn remains of unknown type, so my question is directed towards that API.
Target(s) affected by this defect ?
Artemis Thing Plus (maybe all the Artemis boards)
Toolchain(s) (name and version) displaying this defect ?
ARMC 6.14
What version of Mbed-os are you using (tag or sha) ?
Mbed OS V6.3
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
Mbed Studio V1.3.0
How is this defect reproduced ?
Try to compile any code using these APIs.
The text was updated successfully, but these errors were encountered:
idea--list
changed the title
Status of DigitalIn, InterruptIn and AnalogIn APIs
Status of AnalogIn API
Oct 31, 2020
Description of defect
Can not use
DigitalIn, InterruptIn,AnalogIn APIs while programming the Artemis Thing Plus. Mbed Studio tells these are unknown type names. My question is: is this a bug or are these API still unimplemented for the Apollo3 MCU? If so, is there an estimated time when these get implemented?EDIT:
After restarting my computer only AnalogIn remains of unknown type, so my question is directed towards that API.
Target(s) affected by this defect ?
Artemis Thing Plus (maybe all the Artemis boards)
Toolchain(s) (name and version) displaying this defect ?
ARMC 6.14
What version of Mbed-os are you using (tag or sha) ?
Mbed OS V6.3
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
Mbed Studio V1.3.0
How is this defect reproduced ?
Try to compile any code using these APIs.
The text was updated successfully, but these errors were encountered: