unCleanCode

@gtalusan Were you able to fix the problem? I'm currently trying to get lower than 1.2mA in advertising I found lot of articles/forums where people say they have around 0.1-0.2mA...

And what's your current consumption after that? How did you hard reset it?

Thanks! I'll test it today Were you ever using DEEP SLEEP mode?

My device is also powered by 2x18650 3000mAh. Simple calculations shown me that most of the current consumed in advertising mode when device is waiting for connection and doing no...

Wow, I just found that my second board works perfectly fine with exactly the same code (consumptio in advertising is below 100uA), but second one is around 300-400uA ! Do...

Same for me. Also, COL4 doesn't seem to be working It looks like the problem with all P1.xx pins (P1.00-P1.09)

Btw, in order to make micro:bit v2 board work I was required to fix boards.txt file: ``` # BBCmicrobitV2.menu.softdevice.none=None # BBCmicrobitV2.menu.softdevice.none.softdevice=none # BBCmicrobitV2.menu.softdevice.none.softdeviceversion= BBCmicrobitV2.menu.softdevice.s132=S132 BBCmicrobitV2.menu.softdevice.s132.softdevice=s132 BBCmicrobitV2.menu.softdevice.s132.softdeviceversion=2.0.1 BBCmicrobitV2.menu.softdevice.s132.upload.maximum_size=409600 BBCmicrobitV2.menu.softdevice.s132.build.extra_flags=-DNRF52 -DS132 -DNRF51_S132...

Btw, S132 is already updated to 7.2.0, why still use 2.0.1 ?

I might be wrong, but I see that nRF52.h struct NRF_GPIO_Type has field: `PIN_CNF[32];` which means that when we do: ``` NRF_GPIO_Type* port = digitalPinToPort(6); uint32_t pin = digitalPinToPin(6); ```...

Ok, I was able to make it work (both the LOGO pin and all P1 pins) by commenting in file: components/device/nrf.h line #95: ``` /* Redefine "old" too-generic name NRF52...