Not able to debug using VS code.

[98918atul]

Hello,

I'm using nrf52832 as bluetooth mesh node and programming it through VS code.

Im able to build and upload the code but not able to debug.

After enabling the debug configuration and running it, im only able to discover it in nrf mesh app but able to provision it.

can you guys please provide any support on this, is there any more needed to be done.

Regards

[AHaug]

Hi,

I've picked up your case and will be working on helping you. But I need some more information and clarification.

I'm using nrf52832 as bluetooth mesh node and programming it through VS code.

• Which version of NCS are you using?
• Are you running a Nordic sample without modifications? If so, which?

After enabling the debug configuration and running it, im only able to discover it in nrf mesh app but able to provision it.

I don't quite understand this. You can both discover it and provision it if debug configuration is enabled? What happens if you disable it?

Can you provide me with a step-by-step guide for how to recreate what you are observing?

Kind regards,
Andreas  

[98918atul]

Im using v2.3.0 NCS and light_ctrl example without any modification.  Initially i was able to discover the device through nrf mesh app and while provisioning it was showing "Initial Configuration failed" during debugging. But now I'm not able to discover even i have erased and the uploaded the firmware. Please give some suggestions on this.

[98918atul]

I have started debugging, but not able to discover even in nrf connect and same with nrf mesh.

[AHaug]

Hi,

1. By "light_ctrl" sample, do you mean https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/mesh/light_ctrl/README.html? 
2. Which phone and phone OS are you using?
3. Which version of the nRF Mesh app are you using?
4. Do you see the same behaviour when using 
5. Have you tried
   1. Remove the build folder
   2. Build the firmware once more
   3. Open a terminal and enter nrfjprog -e to erase all on the chip. You can also do this in VS Code under connected devices 
   4. Flash the new firmware with west flash --recover or by pressing this button in VS Code
       

Do you still see the same after repeating step 3?

Do you see the same with other mesh samples?

Kind regards,
Andreas

[98918atul]

 which option we should select for debugging out of this four.

[AHaug]

Hi,

Please answer the previous asked questions. 

Kind regards,
Andreas