is there any slick way to control the menuConfig selections programmatically? Probably not in the way you are thinking. The contents of the sdkconfig file are macro definitions, anywhere they appear in the code, they are replaced with that value that macro represents. What this means is once the co...

I'm not sure what exactly you did next but you should know the CP2102N has two power modes. Bus powered is where VBUS is attached to VREGIN like you have. In this case VDD become a 3.3 volt OUTPUT and should not also have VBUS connected to it. My prior suggestion was connecting RSTb to VDD

Not exactly sure if this is would cause failure to enumerate (I use the QFN24 version, with the VIO pin) but it appears RSTb should be tied to VDD not VBUS. 2.1 Power In all cases, a 1 kΩ pull-up on the RSTb pin is recommended. This pull-up should be tied to VIO on devices that have it. On devices w...

wowee! took a fair bit of hacking but I found my issue. It's strange this worked at all and clearly I need a better understand of passing pointers to FreeRTOS Queues. It was a two part issue, first I was initializing my Queue incorrectly. dio_event_queue = xQueueCreate(10, sizeof(lora32_cfg_t)); sho...

The crux of my issue is that I am unable to increment a value on a pointer to a typedef struct that is acquired from xQueueRecieve. The setup is a very standard long running task that waits for xQueueReceive to be fed from the GPIO ISR. The entirety of the code can be found here and I will call out ...

Yes! I wanted to reply to that but apparently replies are disabled on news. This is something I've been thinking about for a while and would love to sign up, I've got at least 2 drivers ready to go and would probably motivate me to shape up a couple more.

Yes, this does work. The application I'm currently working on does like this.... * ble init... * from on_sync... * start advertising * start discovery * in ble_gap_event .... * use BLE_GAP_EVENT_DISC to handle client connectiong * on BLE_GAP_EVENT_CONNECT, DISCONNECT, ADV_COMPLETE restart advertisin...

First and foremost from your original post, you should check the date code on your device to see if it does in fact have this hardware issue. After 1639 the issue has been fixed. https://www.silabs.com/documents/public/pcns/PCN-1611215-CP2102N-Datasheet-and-Errata-Update.pdf ...back to debugging... ...

Welp, I'm still at a loss as to why this will not work outside ESP32 Arduino 1.0.2 so I've filed a bug.

https://github.com/espressif/esp-idf/issues/4015

This is a known issue.
https://github.com/espressif/esp-idf/issues/3948
That suggest checking out a specific version, if you need something after that, I had limited success with running 'monitor flash build'