is there way to temporarily disable incremental deploy or trigger a full deploy from VS ide? VS 2022 ESP32 issues with incremental deployment requires nanoff flash to reset

[brianro]

I detailed log below from build output for issue. (It happens fairly often)

My ESP32 on ESP32_BLE_REV0 fails incremental deployments with "No reply from nanoDevice"

I have to nanoff to recover:

nanoff --update --platform esp32 --target ESP32_BLE_REV0 --serialport com5

LOG

13:16:28.931 [Starting deployment transaction from v2022.14.1.1+8a5fd66472]
13:16:28.946 [Try to get exclusive access to the nanoDevice]
13:16:28.946 [Starting debug engine on nanoDevice]
13:16:28.946 [Connecting to debugger engine...OK]
13:16:29.137 [Assemblies to deploy:]
13:16:29.137 [Assembly: FanControlApp v1.0.0.0 (3372 bytes)]
13:16:29.154 [Assembly: nanoFramework.System.Collections v1.5.67.0 (4240 bytes)]
13:16:29.202 [Assembly: nanoFramework.Hardware.Esp32 v1.6.34.0 (12176 bytes)]
13:16:29.202 [Assembly: nanoFramework.Device.Bluetooth v1.1.115.0 (54180 bytes)]
13:16:29.202 [Assembly: mscorlib v1.17.11.0 (32536 bytes)]
13:16:29.202 [Assembly: UnitsNet.RelativeHumidity v5.75.0.0 (1240 bytes)]
13:16:29.202 [Assembly: nanoFramework.System.Text v1.3.42.0 (5432 bytes)]
13:16:29.202 [Assembly: nanoFramework.Runtime.Native v1.7.11.0 (1620 bytes)]
13:16:29.202 [Assembly: Iot.Device.Am2320 v1.2.0.0 (2900 bytes)]
13:16:29.202 [Assembly: System.Device.I2c v1.1.29.0 (1756 bytes)]
13:16:29.202 [Assembly: nanoFramework.Runtime.Events v1.11.32.0 (3412 bytes)]
13:16:29.202 [Assembly: System.Device.Model v1.2.0.0 (1356 bytes)]
13:16:29.202 [Assembly: UnitsNet.Temperature v5.75.0.0 (2572 bytes)]
13:16:29.202 [Assembly: System.Buffers.Binary.BinaryPrimitives v1.2.0.0 (3244 bytes)]
13:16:29.217 [Deploying 14 assemblies to device]
13:16:29.297 [Incrementally deploying assemblies to the device]
13:16:29.297 [Erasing block @ 0x001C0000...]
13:16:30.508 [Deploying 1016/130036 bytes.]
13:16:30.555 [Deploying 2032/130036 bytes.]
13:16:30.603 [Deploying 3048/130036 bytes.]
13:16:30.651 [Deploying 4064/130036 bytes.]
13:16:30.699 [Deploying 5080/130036 bytes.]
13:16:30.746 [Deploying 6096/130036 bytes.]
13:16:30.796 [Deploying 7112/130036 bytes.]
13:16:30.841 [Deploying 8128/130036 bytes.]
13:16:30.888 [Deploying 9144/130036 bytes.]
13:16:30.936 [Deploying 10160/130036 bytes.]
13:16:30.983 [Deploying 11176/130036 bytes.]
13:16:31.030 [Deploying 12192/130036 bytes.]
13:16:31.078 [Deploying 13208/130036 bytes.]
13:16:35.097 [Error writing 1016 bytes to device @ 0x001C2FA0. No reply from nanoDevice.]
13:16:35.097 [*** ERROR deploying assemblies to the device ]
13:16:36.100 [Trying again to deploying assemblies]
13:16:36.596 [Incrementally deploying assemblies to the device]
13:16:36.596 [Erasing block @ 0x001C0000...]
13:16:37.810 [Deploying 1016/130036 bytes.]
13:16:37.858 [Deploying 2032/130036 bytes.]
13:16:37.906 [Deploying 3048/130036 bytes.]
13:16:37.953 [Deploying 4064/130036 bytes.]
13:16:38.000 [Deploying 5080/130036 bytes.]
13:16:38.063 [Deploying 6096/130036 bytes.]
13:16:38.111 [Deploying 7112/130036 bytes.]
13:16:38.159 [Deploying 8128/130036 bytes.]
13:16:38.206 [Deploying 9144/130036 bytes.]
13:16:38.253 [Deploying 10160/130036 bytes.]
13:16:38.301 [Deploying 11176/130036 bytes.]
13:16:38.349 [Deploying 12192/130036 bytes.]
13:16:38.396 [Deploying 13208/130036 bytes.]
13:16:38.444 [Deploying 14224/130036 bytes.]
13:16:38.491 [Deploying 15240/130036 bytes.]
13:16:38.539 [Deploying 16256/130036 bytes.]
13:16:38.587 [Deploying 17272/130036 bytes.]
13:16:38.635 [Deploying 18288/130036 bytes.]
13:16:38.682 [Deploying 19304/130036 bytes.]
13:16:42.748 [Error writing 1016 bytes to device @ 0x001C4770. No reply from nanoDevice.]
13:16:42.748 [ ERROR deploying assemblies to the device ]
13:16:42.700 [ ERROR: deployment failed ***]

[alberk8]

Normally, you just add unplug and plug in the USB for it to detect and then you can redploy. Also in debug mode add a sleep on the first line of your code.

 public static void Main()
  {
#if DEBUG
         Thread.Sleep(1000);
#endif
// -----
}

[josesimoes]

We only have full deploy. Meaning that it always deploys the full content for the deployment region.
Having said that: if you're consistently seeing these errors, most likely related with flash writing. That could be caused by issues with power supply: failure to deliver required power, instability, etc. Don't know what it is supplying your board/ESP32. Check cable. Power supply and such.

[brianro]

It is intermittent but the entire process is inconsistent. unplugging the USB and re-plugging doesn't fix the issue. Only a nanoff flash meaning the entire flash becomes corrupted. The device is not "non responsive", that is just what the log says.

This behavior does typically start happening after an exception was thrown in the app.

How does the thread.sleep help in this situation?

Incremental not supported?

What does this mean in the log? " [Incrementally deploying assemblies to the device]"