hi Hxin,

Sorry for the late response. 
Does the device enter energy mode (e.g., EM2) immediately after reset in your project? Any change if connect the board to other USB port without any hub?

Thanks

Some of the peripherals contribute part of the current consumption, please refer to the example here for a better test result.

I would like to measure a low-level and a high-level of voltage from the IADC, preferably storing them into a DMA buffer and ISRing me when the scan is complete (where I'll switch the DMA target to "bank b" while I process A ; to make a circular buffer).

I see that there are 2x Configuration groups, but I'm not sure  how they get chosen...

Ideally, I'd like to scan (all single-ended and with respect to GND and VDD[3v3]):

STRAIN [P26, 0-1V,HiGain], Vin [P25, 0-3v3, Gain1], VBGR [1.21V,Gain1],STRAIN [P26, 0-1V,Gain1],

and repeat at 300KHz or so.

The thinking is that I can sample the strain gauge at 8x gain for lower values (even better if I can use the VBGR as the vref for that input), and change it to 4x, 2x, or 1x as the signal gets larger...  Vin is from the power supplies, conditioned to 0-3v3 from 0-360V, and it does not need to be sampled quickly; I could even measure it at start up and then quit.

I hope I can measure VBGR with respect to Vin to eliminate errors coming from VDD.

...

The wrinkle is...you can only program IADC_CFGx when the ADC is disabled... so I was thinking of IADC_CFG0 = Hi Gain, IADC_CFG1=1x, and if I got overrange on STRAIN0, but a low value (half scale or less) on STRAIN1, I'd have to shut it down, reprogram all the regs for the new 2x gain, and restart.

Is that correct, or am I overlooking a simpler way?

Question #2 - Does this chip have a temperature sensor?

In general, the node will increase pstore_write_interval_elem_seq after reset, and it doesn't make sense that you will get a lower sequence number after reset except the sequence number was exhausted, if that is the case, you need to start the IV update if the node is close to exhausting the sequence number.

Please see the KBA below for how does our stack deal with the sequence number, and how to start the IV update procedure in your application.
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2019/09/02/iv_update_recoveryprocedureandsequencenumber-t90G

In general, the node will increase pstore_write_interval_elem_seq after reset, and it doesn't make sense that you will get a lower sequence number after reset except the sequence number was exhausted, if that is the case, you need to start the IV update if the node is close to exhausting the sequence number.

Please see the KBA below for how does our stack deal with the sequence number, and how to start the IV update procedure n your application.
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2019/09/02/iv_update_recoveryprocedureandsequencenumber-t90G

In general, the node will increase pstore_write_interval_elem_seq after reset, and it doesn't make sense that you will get a lower sequence number after reset except the sequence number was exhausted, if that is the case, you need to start the IV update if the node is close to exhausting the sequence number.

Please see the KBA below for how does our stack deal with the sequence number, and how to start the IV update procedure.
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2019/09/02/iv_update_recoveryprocedureandsequencenumber-t90G

In general, the node will increase pstore_write_interval_elem_seq after reset, and it doesn't make sense that you will get a lower sequence number after reset except the sequence number was exhausted, if that is the case, you need to start the IV update if the node is close to exhausting the sequence number.

Please see the KBA below for how does our stack deal with the sequence number, and how to start the IV update procedure.
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2019/09/02/iv_update_recoveryprocedureandsequencenumber-t90G

As far as I know, the BG22 will only have support for LPN because of the limited RAM, and the Bluetooth mesh examples for BG22 are not available in the Simplicity Studio at this moment.
Regarding to the questions about the roadmap and schedule, please feel free to contact with our sales or marketing.
https://www.silabs.com/about-us/contact-sales

hi Richard S,

Sorry for the late response. If you are looking to use the NVM3 with the soc-empty project, please see section "2.5 Using NVM3 with the Bluetooth SDK" of AN1135 for guidance.