Target
EVK-NINA-B112
Toolchain:
GCC_ARM
Toolchain version:
mbed-cli version:
1.2.2
mbed-os sha:
a5f1426
DAPLink version:
0244
Expected behavior
Sending "break" over serial should reset the MCU.
Actual behavior
Sending "break" over serial does NOT reset the MCU.
Steps to reproduce
Also note HW flow control is disabled for the target in mbed_app.json. With FC enabled, the application does not run at all.
@andreaslarssonublox @c1728p9 @0xc0170 , could you please check? Thanks.
@ARMmbed/team-ublox
Hi,
Some questions:
What debug chip is used?
Schematics?
What is the target here, EVK-NINA-B112(#5838) or MTB_UBLOX_NINA_B1(#5837)?
Thanks @andreaslarssonublox . Debug chip = LPC11U35 . I'm not sure if I can share the schematics at the moment. Let me check that with @chris-styles. Target = MTB_UBLOX_NINA_B1 but it is using the NINA-B112 module (same as the EVK-NINA-B112) and brings out the Tx, Rx, NRESET pins from the module to the breakout board that are mapped in PinNames.h as part for PR #5837 ..
@andreaslarssonublox .. bump!
Hi, I looked at https://github.com/ARMmbed/DAPLink but could not find any support for the combination LPC11U35 and NINA-B1 and we don't have any hardware(with LPC11U35) to test with so might be hard for us to debug?
Thanks @andreaslarssonublox .. in that case, I'll try to debug locally.
This is DAPLink fix. New version of DAPLink here: https://github.com/ARMmbed/DAPLink/pull/376 fixes this issue.
Closing. Thanks!