New laptop struggles to deploy

LucaP · April 23, 2024, 1:48pm

I recently got a new laptop from HP, but it has struggles deploying software to our SC20100S based modules.

Programming firmware though the tinyclr config works just fine, but when deploying an app with visual studio, it fails almost every single time. The exact fault differs. Sometimes it only flashes half of the sectors, leading to an a30000 error at startup. Sometimes it flashes completely, reboots the module and hangs for a minute and then visual studio crashes.

There is nothing wrong with the VS project. It works on all other computers we’ve tried. The boards are also fine because my colleages have no issue programming these exact boards with their machines. All the boards are externally powered by a 24V DC power supply so I don’t think USB power output is at fault here either.

I’ve tried updating windows and updating all the drivers. This also does not solve the problem.
I have tried deleting the device in device manager and then replugging the board, also does not fix it.

The only thing I have found that seems to fix it somewhat, is to force windows to use the win8 USB driver that can be downloaded from the ghi site. However, this works once or twice before the old issue comes back.

Is there a way to enable verbose logging or anything else so that I can provide you with a detailed log from the TinyCLR visual studio extension?

Dat_Tran · April 23, 2024, 2:00pm

Is VS community, Enterprise or Professional?

LucaP · April 23, 2024, 2:01pm

Community 2022, we are running this one on all of our machines.

Dat_Tran · April 23, 2024, 2:12pm

You are one of our experts, I don’t think we need to ask you more questions.

I am waiting for other people’s suggestions

LucaP · April 23, 2024, 2:13pm

There is no log files I can collect that would provide any insight? To me it seems like a driver error of some sort.

Dat_Tran · April 23, 2024, 2:19pm

No, what window OS please? Win10 or Win11 no need special driver for USB.
Are you using QSPI as external deployment?

LucaP · April 23, 2024, 2:22pm

Latest update of W11.
External deployment is not enabled on these boards.

mcalsyn · April 23, 2024, 4:34pm

Is there anything in the Event Viewer? Right after you hit an error, run eventvwr and look in the System, Application, and Security folders for any errors or warnings related to VS or USB. There might also be driver related folders, but I don’t recall and I am currently on a Mac.

Visual Studio also emits a log file and you can find more info about that here : Use the Activity Log to debug and add entries - Visual Studio (Windows) | Microsoft Learn

I don’t have any recommendations for a fix, but digging into those log files may provide more actionable information.

skeller · April 23, 2024, 5:06pm

Just throwing stuff against the wall. Is there a difference between the various computers in regards to USB 2 and USB 3?

Dat_Tran · April 26, 2024, 1:20pm

Is it I9 or I7 please? and yes, the USB port is 2 or 3?

QOTF-Alexi · April 26, 2024, 1:39pm

If the laptop has a Ryzen processor, I have had some bad experiences with mobile and early AMD Ryzen USB controllers, especially with debuggers, VCP’s and things that require tight command timing & clock signals. What sometimes helped for me was using a powered USB 2.0 hub (that uses its own, usually Realtek or Cirrus Logic, controller IC). The issue does not seem to affect controllers from other brands than AMD.

LucaP · April 26, 2024, 8:17pm

Thank you all for your help. I reinstalled my laptop from a clean windows 10 ISO and now it seems to work just fine. Im not sure what the issue was. It is an intel i7 with a USB3 port anyways. Might’ve been some HP related bloatware…

I’ll test more over the coming days and will report back if I find any issue.

LucaP · May 22, 2024, 6:57pm

The issue is back, but it might be in a different form.

It seems like hitting deploy in visual studio activates the action twice. My output window is showing information about the device deployment DLLs, switches to writing sectors, then halfway thorugh switches back to device deployment DLLs and then back to writing sectors (which skips halfs the sectors this time). Most of the time, this results in a failed deployment with a crashed visual studio instance. Sometimes, deployment starts but the code executes much slower than usual. Using a breakpoint and every line of code takes between 1s and 5s…

Any reason the action is activated double?

dcyonce · August 2, 2024, 7:41pm

Dat,
I am also STILL having this problem. I brought it up about a year ago, but never got a fix.
Any plan of improving Visual Studio Extension? - TinyCLR OS - GHI Electronics’ Forums

Got a new, much faster PC this week, and the problem is now much, much worse. I cannot deploy firmware to GHI modules at all. As I’ve said before … “the faster the PC, the worse the problem”. This new PC I just received is an i9-14900k running at ~5GHz. 64MB RAM. Very, very fast.

Running Visual Studio Enterprise 2022 (64-bit) v17.10.5 with TinyCLR add-in 2.2.2.1100
GHI Firmware 2.2.2.1000 on a SC13048. “Extend Deployment” checked.
No other USB devices plugged in other than the SC13048 I’m trying to load.

Here’s an example log:

Looking for a device on transport 'USB'.
Found device port 'USB' with ID '60998b45-33dc-4229-9d41-5c285e68ea19' for transport 'Usb'.
Starting device deployment.
Attempting to connect to device 'USB:SC13048': iteration 0.
Opening port '\\?\usb#vid_1b9f&pid_5012#6&76f112&0&2#{c13bcfe9-5e84-4187-9baa-45597ffcbb6f}'.
Attaching debugger engine.
Debugger engine attached.
Generating device specific assemblies.
	- Power Monitor v1.0.0.0 with size 556 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\Power Monitor.pe'.
	- AtlantisDevelopment.TinyCLR.Core v2024.4.19.32029 with size 21,340 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\AtlantisDevelopment.TinyCLR.Core.pe'.
	- AtlantisDevelopment.TinyCLR.GNSS v2024.4.19.32031 with size 15,960 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\AtlantisDevelopment.TinyCLR.GNSS.pe'.
	- AtlantisDevelopment.TinyCLR.SDCardDriver v2024.3.23.32032 with size 26,716 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\AtlantisDevelopment.TinyCLR.SDCardDriver.pe'.
	- mscorlib v2.2.2.1000 with size 72,556 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\mscorlib.pe'.
	- Syzydyne.ChassisTracker v2024.7.25.38206 with size 182,716 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\Syzydyne.ChassisTracker.pe'.
	- GHIElectronics.TinyCLR.Devices.Gpio v2.2.2.1000 with size 4,880 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Gpio.pe'.
	- GHIElectronics.TinyCLR.Devices.I2c v2.2.2.1000 with size 10,464 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.I2c.pe'.
	- GHIElectronics.TinyCLR.Devices.Rtc v2.2.2.1000 with size 3,316 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Rtc.pe'.
	- GHIElectronics.TinyCLR.Devices.Spi v2.2.2.1000 with size 6,284 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Spi.pe'.
	- GHIElectronics.TinyCLR.Devices.Storage v2.2.2.1000 with size 3,432 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Storage.pe'.
	- GHIElectronics.TinyCLR.Devices.Uart v2.2.2.1000 with size 8,012 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Uart.pe'.
	- GHIElectronics.TinyCLR.Devices.Watchdog v2.2.2.1000 with size 1,652 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Watchdog.pe'.
	- GHIElectronics.TinyCLR.IO v2.2.2.1000 with size 21,144 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.IO.pe'.
	- GHIElectronics.TinyCLR.IO.TinyFileSystem v2.2.2.1000 with size 16,372 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.IO.TinyFileSystem.pe'.
	- GHIElectronics.TinyCLR.Native v2.2.2.1000 with size 6,200 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Native.pe'.
	- GHIElectronics.TinyCLR.Networking v2.2.2.1000 with size 13,072 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Networking.pe'.
	- GHIElectronics.TinyCLR.Update v2.2.2.1000 with size 4,440 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Update.pe'.
Total deployment size is 419,112 bytes.
Incrementally deploying assemblies to the device:
Allocating assemblies:
	- Address: 0x08047000 => Syzydyne.ChassisTracker 
	- Address: 0x90A00000 => mscorlib 
	- Address: 0x080739BC => AtlantisDevelopment.TinyCLR.SDCardDriver 
	- Address: 0x90A11B6C => AtlantisDevelopment.TinyCLR.Core 
	- Address: 0x90A16EC8 => GHIElectronics.TinyCLR.IO 
	- Address: 0x90A1C160 => GHIElectronics.TinyCLR.IO.TinyFileSystem 
	- Address: 0x90A20154 => AtlantisDevelopment.TinyCLR.GNSS 
	- Address: 0x0807A218 => GHIElectronics.TinyCLR.Networking 
	- Address: 0x90A23FAC => GHIElectronics.TinyCLR.Devices.I2c 
	- Address: 0x90A2688C => GHIElectronics.TinyCLR.Devices.Uart 
	- Address: 0x90A287D8 => GHIElectronics.TinyCLR.Devices.Spi 
	- Address: 0x90A2A064 => GHIElectronics.TinyCLR.Native 
	- Address: 0x90A2B89C => GHIElectronics.TinyCLR.Devices.Gpio 
	- Address: 0x90A2CBAC => GHIElectronics.TinyCLR.Update 
	- Address: 0x90A2DD04 => GHIElectronics.TinyCLR.Devices.Storage 
	- Address: 0x90A2EA6C => GHIElectronics.TinyCLR.Devices.Rtc 
	- Address: 0x90A2F760 => GHIElectronics.TinyCLR.Devices.Watchdog 
	- Address: 0x0807D528 => Power Monitor 
Deploying assemblies:
	- Writing sector 1: Ignored (same crc)
	- Writing sector 2: Ignored (same crc)
	- Writing sector 3: Ignored (same crc)
	- Writing sector 4: Ignored (same crc)
	- Checking status: sector 5, address @0x08049000...
	- Checking status: sector 5, address @0x08049000...
	- Checking status: sector 5, address @0x08049000...
	- Checking status: sector 5, address @0x08049000...
	- Checking status: sector 5, address @0x08049000...
FAILED to get status device memory @0x08049000
Assemblies not successfully deployed to the device.
Deployment to the device was not successful.

And another example:

Looking for a device on transport 'USB'.
Found device port 'USB' with ID '60998b45-33dc-4229-9d41-5c285e68ea19' for transport 'Usb'.
Starting device deployment.
Attempting to connect to device 'USB:SC13048': iteration 0.
Opening port '\\?\usb#vid_1b9f&pid_5012#6&76f112&0&2#{c13bcfe9-5e84-4187-9baa-45597ffcbb6f}'.
Attaching debugger engine.
Debugger engine attached.
Generating device specific assemblies.
	- Power Monitor v1.0.0.0 with size 556 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\Power Monitor.pe'.
	- AtlantisDevelopment.TinyCLR.Core v2024.4.19.32029 with size 21,340 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\AtlantisDevelopment.TinyCLR.Core.pe'.
	- AtlantisDevelopment.TinyCLR.GNSS v2024.4.19.32031 with size 15,960 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\AtlantisDevelopment.TinyCLR.GNSS.pe'.
	- AtlantisDevelopment.TinyCLR.SDCardDriver v2024.3.23.32032 with size 26,716 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\AtlantisDevelopment.TinyCLR.SDCardDriver.pe'.
	- mscorlib v2.2.2.1000 with size 72,556 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\mscorlib.pe'.
	- Syzydyne.ChassisTracker v2024.7.25.38206 with size 182,716 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\Syzydyne.ChassisTracker.pe'.
	- GHIElectronics.TinyCLR.Devices.Gpio v2.2.2.1000 with size 4,880 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Gpio.pe'.
	- GHIElectronics.TinyCLR.Devices.I2c v2.2.2.1000 with size 10,464 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.I2c.pe'.
	- GHIElectronics.TinyCLR.Devices.Rtc v2.2.2.1000 with size 3,316 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Rtc.pe'.
	- GHIElectronics.TinyCLR.Devices.Spi v2.2.2.1000 with size 6,284 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Spi.pe'.
	- GHIElectronics.TinyCLR.Devices.Storage v2.2.2.1000 with size 3,432 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Storage.pe'.
	- GHIElectronics.TinyCLR.Devices.Uart v2.2.2.1000 with size 8,012 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Uart.pe'.
	- GHIElectronics.TinyCLR.Devices.Watchdog v2.2.2.1000 with size 1,652 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Watchdog.pe'.
	- GHIElectronics.TinyCLR.IO v2.2.2.1000 with size 21,144 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.IO.pe'.
	- GHIElectronics.TinyCLR.IO.TinyFileSystem v2.2.2.1000 with size 16,372 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.IO.TinyFileSystem.pe'.
	- GHIElectronics.TinyCLR.Native v2.2.2.1000 with size 6,200 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Native.pe'.
	- GHIElectronics.TinyCLR.Networking v2.2.2.1000 with size 13,072 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Networking.pe'.
	- GHIElectronics.TinyCLR.Update v2.2.2.1000 with size 4,440 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\Power Monitor\bin\Debug\pe\GHIElectronics.TinyCLR.Update.pe'.
Total deployment size is 419,112 bytes.
Incrementally deploying assemblies to the device:
Allocating assemblies:
	- Address: 0x08047000 => Syzydyne.ChassisTracker 
	- Address: 0x90A00000 => mscorlib 
	- Address: 0x080739BC => AtlantisDevelopment.TinyCLR.SDCardDriver 
	- Address: 0x90A11B6C => AtlantisDevelopment.TinyCLR.Core 
	- Address: 0x90A16EC8 => GHIElectronics.TinyCLR.IO 
	- Address: 0x90A1C160 => GHIElectronics.TinyCLR.IO.TinyFileSystem 
	- Address: 0x90A20154 => AtlantisDevelopment.TinyCLR.GNSS 
	- Address: 0x0807A218 => GHIElectronics.TinyCLR.Networking 
	- Address: 0x90A23FAC => GHIElectronics.TinyCLR.Devices.I2c 
	- Address: 0x90A2688C => GHIElectronics.TinyCLR.Devices.Uart 
	- Address: 0x90A287D8 => GHIElectronics.TinyCLR.Devices.Spi 
	- Address: 0x90A2A064 => GHIElectronics.TinyCLR.Native 
	- Address: 0x90A2B89C => GHIElectronics.TinyCLR.Devices.Gpio 
	- Address: 0x90A2CBAC => GHIElectronics.TinyCLR.Update 
	- Address: 0x90A2DD04 => GHIElectronics.TinyCLR.Devices.Storage 
	- Address: 0x90A2EA6C => GHIElectronics.TinyCLR.Devices.Rtc 
	- Address: 0x90A2F760 => GHIElectronics.TinyCLR.Devices.Watchdog 
	- Address: 0x0807D528 => Power Monitor 
Deploying assemblies:
	- Writing sector 1: Ignored (same crc)
	- Writing sector 2: Ignored (same crc)
	- Writing sector 3: Ignored (same crc)
	- Writing sector 4: Ignored (same crc)
	- Writing sector 5: Ignored (same crc)
	- Writing sector 6: Ignored (same crc)
	- Writing sector 7: Ignored (same crc)
	- Writing sector 8: Ignored (same crc)
	- Writing sector 9: Ignored (same crc)
	- Writing sector 10: Ignored (same crc)
	- Writing sector 11: Ignored (same crc)
	- Writing sector 12: Ignored (same crc)
	- Checking status: sector 13, address @0x0804D000...
	- Writing sector 13: Ignored (same crc)
	- Writing sector 14: Ignored (same crc)
	- Writing sector 15: Ignored (same crc)
	- Writing sector 16: Ignored (same crc)
	- Writing sector 17: Ignored (same crc)
	- Writing sector 18: Ignored (same crc)
	- Writing sector 19: Ignored (same crc)
	- Writing sector 20: Ignored (same crc)
	- Writing sector 21: Ignored (same crc)
	- Checking status: sector 22, address @0x08051800...
	- Writing sector 22: Ignored (same crc)
	- Writing sector 23: Ignored (same crc)
	- Writing sector 24: Ignored (same crc)
	- Writing sector 25: Ignored (same crc)
	- Writing sector 26: Ignored (same crc)
	- Writing sector 27: Ignored (same crc)
	- Writing sector 28: Ignored (same crc)
	- Writing sector 29: Ignored (same crc)
	- Writing sector 30: Ignored (same crc)
	- Writing sector 31: Ignored (same crc)
	- Writing sector 32: Ignored (same crc)
	- Writing sector 33: Ignored (same crc)
	- Writing sector 34: Ignored (same crc)
	- Checking status: sector 35, address @0x08058000...
	- Writing sector 35: Ignored (same crc)
	- Writing sector 36: Ignored (same crc)
	- Writing sector 37: Ignored (same crc)
	- Writing sector 38: Ignored (same crc)
	- Writing sector 39: Ignored (same crc)
	- Writing sector 40: Ignored (same crc)
	- Writing sector 41: Ignored (same crc)
	- Writing sector 42: Ignored (same crc)
	- Writing sector 43: Ignored (same crc)
	- Writing sector 44: Ignored (same crc)
	- Writing sector 45: Ignored (same crc)
	- Writing sector 46: Ignored (same crc)
	- Writing sector 47: Ignored (same crc)
	- Writing sector 48: Ignored (same crc)
	- Writing sector 49: Ignored (same crc)
	- Writing sector 50: Ignored (same crc)
	- Writing sector 51: Ignored (same crc)
	- Writing sector 52: Ignored (same crc)
	- Writing sector 53: Ignored (same crc)
	- Writing sector 54: Ignored (same crc)
	- Writing sector 55: Ignored (same crc)
	- Writing sector 56: Ignored (same crc)
	- Writing sector 57: Ignored (same crc)
	- Writing sector 58: Ignored (same crc)
	- Writing sector 59: Ignored (same crc)
	- Writing sector 60: Ignored (same crc)
	- Writing sector 61: Ignored (same crc)
	- Writing sector 62: Ignored (same crc)
	- Writing sector 63: Ignored (same crc)
	- Writing sector 64: Ignored (same crc)
	- Writing sector 65: Ignored (same crc)
	- Writing sector 66: Ignored (same crc)
	- Writing sector 67: Ignored (same crc)
	- Writing sector 68: Ignored (same crc)
	- Writing sector 69: Ignored (same crc)
	- Writing sector 70: Ignored (same crc)
	- Writing sector 71: Ignored (same crc)
	- Writing sector 72: Ignored (same crc)
	- Writing sector 73: Ignored (same crc)
	- Writing sector 74: Ignored (same crc)
	- Writing sector 75: Ignored (same crc)
	- Writing sector 76: Ignored (same crc)
	- Writing sector 77: Ignored (same crc)
	- Writing sector 78: Ignored (same crc)
	- Writing sector 79: Ignored (same crc)
	- Writing sector 80: Ignored (same crc)
	- Writing sector 81: Ignored (same crc)
	- Writing sector 82: Ignored (same crc)
	- Writing sector 83: Ignored (same crc)
	- Writing sector 84: Ignored (same crc)
	- Writing sector 85: Ignored (same crc)
	- Writing sector 86: Ignored (same crc)
	- Writing sector 87: Ignored (same crc)
	- Writing sector 88: Ignored (same crc)
	- Writing sector 89: Ignored (same crc)
	- Writing sector 90: Ignored (same crc)
	- Writing sector 91: Ignored (same crc)
	- Writing sector 92: Ignored (same crc)
	- Writing sector 93: Ignored (same crc)
	- Writing sector 94: Ignored (same crc)
	- Writing sector 95: Ignored (same crc)
	- Writing sector 96: Ignored (same crc)
	- Writing sector 97: Ignored (same crc)
	- Writing sector 98: Ignored (same crc)
	- Writing sector 99: Ignored (same crc)
	- Writing sector 100: Ignored (same crc)
	- Writing sector 101: Ignored (same crc)
	- Writing sector 102: Ignored (same crc)
	- Writing sector 103: Ignored (same crc)
	- Writing sector 104: Ignored (same crc)
	- Writing sector 105: Ignored (same crc)
	- Writing sector 106: Ignored (same crc)
	- Writing sector 107: Ignored (same crc)
	- Writing sector 108: Ignored (same crc)
	- Writing sector 109: Ignored (same crc)
	- Writing sector 110: Ignored (same crc)
	- Writing sector 111: Ignored (same crc)
	- Writing sector 112: Ignored (same crc)
	- Writing sector 113: Ignored (same crc)
	- Writing sector 114: Ignored (same crc)
	- Writing sector 115: Ignored (same crc)
	- Writing sector 116: Ignored (same crc)
	- Writing sector 117: Ignored (same crc)
	- Writing sector 118: Ignored (same crc)
	- Writing sector 119: Ignored (same crc)
	- Writing sector 120: Ignored (same crc)
	- Writing sector 121: Ignored (same crc)
	- Checking status: sector 122, address @0x90A0B000...
	- Writing sector 122: Ignored (same crc)
	- Writing sector 123: Ignored (same crc)
	- Writing sector 124: Ignored (same crc)
	- Writing sector 125: Ignored (same crc)
	- Writing sector 126: Ignored (same crc)
	- Writing sector 127: Ignored (same crc)
	- Writing sector 128: Ignored (same crc)
	- Writing sector 129: Ignored (same crc)
	- Writing sector 130: Ignored (same crc)
	- Writing sector 131: Ignored (same crc)
	- Writing sector 132: Ignored (same crc)
	- Writing sector 133: Ignored (same crc)
	- Writing sector 134: Ignored (same crc)
	- Writing sector 135: Ignored (same crc)
	- Writing sector 136: Ignored (same crc)
	- Writing sector 137: Ignored (same crc)
	- Writing sector 138: Ignored (same crc)
	- Writing sector 139: Ignored (same crc)
	- Writing sector 140: Ignored (same crc)
	- Writing sector 141: Ignored (same crc)
	- Writing sector 142: Ignored (same crc)
	- Writing sector 143: Ignored (same crc)
	- Writing sector 144: Ignored (same crc)
	- Writing sector 145: Ignored (same crc)
	- Writing sector 146: Ignored (same crc)
	- Writing sector 147: Ignored (same crc)
	- Writing sector 148: Ignored (same crc)
	- Writing sector 149: Ignored (same crc)
	- Writing sector 150: Ignored (same crc)
	- Writing sector 151: Ignored (same crc)
	- Writing sector 152: Ignored (same crc)
	- Writing sector 153: Ignored (same crc)
	- Writing sector 154: Ignored (same crc)
	- Writing sector 155: Ignored (same crc)
	- Writing sector 156: Ignored (same crc)
	- Writing sector 157: Ignored (same crc)
	- Writing sector 158: Ignored (same crc)
	- Checking status: sector 159, address @0x90A30000...
	- Writing sector 159: Ignored (same crc)
	- Writing sector 160: Ignored (same crc)
	- Writing sector 161: Ignored (same crc)
	- Writing sector 162: Ignored (same crc)
	- Writing sector 163: Ignored (same crc)
	- Writing sector 164: Ignored (same crc)
	- Writing sector 165: Ignored (same crc)
	- Writing sector 166: Ignored (same crc)
	- Writing sector 167: Ignored (same crc)
	- Writing sector 168: Ignored (same crc)
	- Writing sector 169: Ignored (same crc)
	- Writing sector 170: Ignored (same crc)
	- Writing sector 171: Ignored (same crc)
	- Writing sector 172: Ignored (same crc)
	- Writing sector 173: Ignored (same crc)
	- Writing sector 174: Ignored (same crc)
	- Writing sector 175: Ignored (same crc)
	- Writing sector 176: Ignored (same crc)
	- Writing sector 177: Ignored (same crc)
	- Writing sector 178: Ignored (same crc)
	- Writing sector 179: Ignored (same crc)
	- Writing sector 180: Ignored (same crc)
	- Writing sector 181: Ignored (same crc)
	- Writing sector 182: Ignored (same crc)
	- Writing sector 183: Ignored (same crc)
	- Writing sector 184: Ignored (same crc)
	- Writing sector 185: Ignored (same crc)
	- Writing sector 186: Ignored (same crc)
	- Writing sector 187: Ignored (same crc)
	- Writing sector 188: Ignored (same crc)
	- Writing sector 189: Ignored (same crc)
	- Writing sector 190: Ignored (same crc)
	- Writing sector 191: Ignored (same crc)
	- Writing sector 192: Ignored (same crc)
	- Writing sector 193: Ignored (same crc)
	- Writing sector 194: Ignored (same crc)
	- Writing sector 195: Ignored (same crc)
	- Writing sector 196: Ignored (same crc)
	- Writing sector 197: Ignored (same crc)
	- Writing sector 198: Ignored (same crc)
	- Checking status: sector 199, address @0x90A58000...
	- Writing sector 199: Ignored (same crc)
	- Writing sector 200: Ignored (same crc)
	- Writing sector 201: Ignored (same crc)
	- Writing sector 202: Ignored (same crc)
	- Writing sector 203: Ignored (same crc)
	- Writing sector 204: Ignored (same crc)
	- Writing sector 205: Ignored (same crc)
	- Writing sector 206: Ignored (same crc)
	- Writing sector 207: Ignored (same crc)
	- Writing sector 208: Ignored (same crc)
	- Writing sector 209: Ignored (same crc)
	- Writing sector 210: Ignored (same crc)
	- Writing sector 211: Ignored (same crc)
	- Writing sector 212: Ignored (same crc)
	- Writing sector 213: Ignored (same crc)
	- Writing sector 214: Ignored (same crc)
	- Writing sector 215: Ignored (same crc)
	- Writing sector 216: Ignored (same crc)
	- Writing sector 217: Ignored (same crc)
	- Writing sector 218: Ignored (same crc)
	- Writing sector 219: Ignored (same crc)
	- Writing sector 220: Ignored (same crc)
	- Writing sector 221: Ignored (same crc)
	- Writing sector 222: Ignored (same crc)
	- Writing sector 223: Ignored (same crc)
	- Writing sector 224: Ignored (same crc)
	- Writing sector 225: Ignored (same crc)
	- Writing sector 226: Ignored (same crc)
	- Writing sector 227: Ignored (same crc)
	- Writing sector 228: Ignored (same crc)
	- Writing sector 229: Ignored (same crc)
	- Writing sector 230: Ignored (same crc)
	- Writing sector 231: Ignored (same crc)
	- Writing sector 232: Ignored (same crc)
	- Checking status: sector 233, address @0x90A7A000...
	- Writing sector 233: Ignored (same crc)
	- Writing sector 234: Ignored (same crc)
	- Writing sector 235: Ignored (same crc)
	- Writing sector 236: Ignored (same crc)
	- Writing sector 237: Ignored (same crc)
	- Writing sector 238: Ignored (same crc)
	- Writing sector 239: Ignored (same crc)
	- Writing sector 240: Ignored (same crc)
	- Writing sector 241: Ignored (same crc)
	- Writing sector 242: Ignored (same crc)
	- Writing sector 243: Ignored (same crc)
	- Writing sector 244: Ignored (same crc)
	- Writing sector 245: Ignored (same crc)
	- Writing sector 246: Ignored (same crc)
	- Writing sector 247: Ignored (same crc)
	- Writing sector 248: Ignored (same crc)
	- Writing sector 249: Ignored (same crc)
	- Writing sector 250: Ignored (same crc)
	- Writing sector 251: Ignored (same crc)
	- Writing sector 252: Ignored (same crc)
	- Writing sector 253: Ignored (same crc)
	- Writing sector 254: Ignored (same crc)
	- Writing sector 255: Ignored (same crc)
	- Writing sector 256: Ignored (same crc)
	- Writing sector 257: Ignored (same crc)
	- Writing sector 258: Ignored (same crc)
	- Writing sector 259: Ignored (same crc)
	- Writing sector 260: Ignored (same crc)
	- Writing sector 261: Ignored (same crc)
	- Writing sector 262: Ignored (same crc)
	- Writing sector 263: Ignored (same crc)
	- Writing sector 264: Ignored (same crc)
	- Writing sector 265: Ignored (same crc)
	- Writing sector 266: Ignored (same crc)
	- Writing sector 267: Ignored (same crc)
	- Writing sector 268: Ignored (same crc)
	- Writing sector 269: Ignored (same crc)
	- Writing sector 270: Ignored (same crc)
	- Checking status: sector 271, address @0x90AA0000...
	- Writing sector 271: Ignored (same crc)
	- Writing sector 272: Ignored (same crc)
	- Writing sector 273: Ignored (same crc)
	- Writing sector 274: Ignored (same crc)
	- Writing sector 275: Ignored (same crc)
	- Writing sector 276: Ignored (same crc)
	- Writing sector 277: Ignored (same crc)
	- Writing sector 278: Ignored (same crc)
	- Writing sector 279: Ignored (same crc)
	- Writing sector 280: Ignored (same crc)
	- Writing sector 281: Ignored (same crc)
	- Writing sector 282: Ignored (same crc)
	- Writing sector 283: Ignored (same crc)
	- Writing sector 284: Ignored (same crc)
	- Writing sector 285: Ignored (same crc)
	- Writing sector 286: Ignored (same crc)
	- Writing sector 287: Ignored (same crc)
	- Writing sector 288: Ignored (same crc)
	- Writing sector 289: Ignored (same crc)
	- Writing sector 290: Ignored (same crc)
	- Writing sector 291: Ignored (same crc)
	- Writing sector 292: Ignored (same crc)
	- Writing sector 293: Ignored (same crc)
	- Writing sector 294: Ignored (same crc)
	- Writing sector 295: Ignored (same crc)
	- Writing sector 296: Ignored (same crc)
	- Writing sector 297: Ignored (same crc)
	- Writing sector 298: Ignored (same crc)
	- Writing sector 299: Ignored (same crc)
	- Writing sector 300: Ignored (same crc)
	- Writing sector 301: Ignored (same crc)
	- Writing sector 302: Ignored (same crc)
	- Writing sector 303: Ignored (same crc)
	- Writing sector 304: Ignored (same crc)
	- Writing sector 305: Ignored (same crc)
	- Writing sector 306: Ignored (same crc)
	- Checking status: sector 307, address @0x90AC4000...
	- Writing sector 307: Ignored (same crc)
	- Writing sector 308: Ignored (same crc)
	- Writing sector 309: Ignored (same crc)
	- Writing sector 310: Ignored (same crc)
	- Writing sector 311: Ignored (same crc)
	- Writing sector 312: Ignored (same crc)
	- Writing sector 313: Ignored (same crc)
	- Writing sector 314: Ignored (same crc)
	- Writing sector 315: Ignored (same crc)
	- Writing sector 316: Ignored (same crc)
	- Writing sector 317: Ignored (same crc)
	- Writing sector 318: Ignored (same crc)
	- Writing sector 319: Ignored (same crc)
	- Writing sector 320: Ignored (same crc)
	- Writing sector 321: Ignored (same crc)
	- Writing sector 322: Ignored (same crc)
	- Writing sector 323: Ignored (same crc)
	- Writing sector 324: Ignored (same crc)
	- Writing sector 325: Ignored (same crc)
	- Writing sector 326: Ignored (same crc)
	- Writing sector 327: Ignored (same crc)
	- Writing sector 328: Ignored (same crc)
	- Writing sector 329: Ignored (same crc)
	- Writing sector 330: Ignored (same crc)
	- Writing sector 331: Ignored (same crc)
	- Writing sector 332: Ignored (same crc)
	- Writing sector 333: Ignored (same crc)
	- Writing sector 334: Ignored (same crc)
	- Writing sector 335: Ignored (same crc)
	- Writing sector 336: Ignored (same crc)
	- Writing sector 337: Ignored (same crc)
	- Writing sector 338: Ignored (same crc)
	- Writing sector 339: Ignored (same crc)
	- Checking status: sector 340, address @0x90AE5000...
	- Writing sector 340: Ignored (same crc)
	- Writing sector 341: Ignored (same crc)
	- Writing sector 342: Ignored (same crc)
	- Writing sector 343: Ignored (same crc)
	- Writing sector 344: Ignored (same crc)
	- Writing sector 345: Ignored (same crc)
	- Writing sector 346: Ignored (same crc)
	- Writing sector 347: Ignored (same crc)
	- Writing sector 348: Ignored (same crc)
	- Writing sector 349: Ignored (same crc)
	- Writing sector 350: Ignored (same crc)
	- Writing sector 351: Ignored (same crc)
	- Writing sector 352: Ignored (same crc)
	- Writing sector 353: Ignored (same crc)
	- Writing sector 354: Ignored (same crc)
	- Writing sector 355: Ignored (same crc)
	- Writing sector 356: Ignored (same crc)
	- Writing sector 357: Ignored (same crc)
	- Writing sector 358: Ignored (same crc)
	- Writing sector 359: Ignored (same crc)
	- Writing sector 360: Ignored (same crc)
	- Writing sector 361: Ignored (same crc)
	- Writing sector 362: Ignored (same crc)
	- Writing sector 363: Ignored (same crc)
	- Writing sector 364: Ignored (same crc)
	- Writing sector 365: Ignored (same crc)
	- Writing sector 366: Ignored (same crc)
	- Writing sector 367: Ignored (same crc)
	- Writing sector 368: Ignored (same crc)
	- Writing sector 369: Ignored (same crc)
	- Writing sector 370: Ignored (same crc)
	- Writing sector 371: Ignored (same crc)
	- Writing sector 372: Ignored (same crc)
	- Writing sector 373: Ignored (same crc)
	- Writing sector 374: Ignored (same crc)
	- Writing sector 375: Ignored (same crc)
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...
FAILED to get status device memory @0x90B09000
Assemblies not successfully deployed to the device.
Deployment to the device was not successful.

If I slow down the USB bus … copy a giant file to a USB stick at the same time for example. The GHI loader seems to behave a little better. I am “sometimes” able to load firmware using this method.

No other USB issues with this new PC (or the old PC that was also having this problem).
NanoFramework VS Extension never has any USB issues at all. Works every time.

I’m here day and night to figure out this problem. Let me know how I can help … running debug code, capturing logs … whatever is needed !

– Don

Dat_Tran · August 2, 2024, 7:54pm

I remember there is an issue with VS Enterprice.
Try something below and let us know the result:

Use TinyCLR Tool Config, Erase application.
Try to install VS Community ?

But, I still see below sometime on my PC, after updated VS few time, not much and working on it. What device are you using?

- Writing sector 371: Ignored (same crc)
	- Writing sector 372: Ignored (same crc)
	- Writing sector 373: Ignored (same crc)
	- Writing sector 374: Ignored (same crc)
	- Writing sector 375: Ignored (same crc)
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...
	- Checking status: sector 376, address @0x90B09000...

Mike · August 2, 2024, 8:03pm

Would putting an older USB hub between the device and PC help? Might slow it down… Also try a powered hub.

dcyonce · August 2, 2024, 8:57pm

Hey Dat,
Device is our own board with a SC13048 on board.
But, same problem with a PICO.

Cat Herder,
I had the same idea! I tried a couple older and newer USB hubs … and powered hubs.
Doesn’t seem to make much of a difference.

More info …
I was able to load firmware successfully via this strange process …
Reboot the PC. Load firmware within 60 seconds of boot. Seems to work just fine.
After 60 seconds … lots of failures.
I think it must be something else starting up that is interfering with the USB line !!!
But, this is a band new build of Windows 11 Pro on brand new Gigabyte hardware.
I disabled all the services that I could. No changes.

This issue seems to be software related, not hardware.

If you have some debug code to dump more info … I’ll run it !

– Don

LucaP · August 3, 2024, 6:20pm

I think the issue is the speed. It seems like during one of the resets the board gets, it gets back online either too quickly or too late for the tooling to recognize it thus causing the crashes.

I was able to get rid of most of my issues by installing windows 10, realizing my laptop didn’t have ethernet drivers for w10, updating to w11.

Its semi decent now, but still about 50% hit or miss.

dcyonce · August 5, 2024, 2:46pm

Dat,
Glad to see that you can reproduce the problem. Hopefully you can also fix it !

Tried erasing the Application using TinyCLR Config. No change.

Looking for a device on transport 'USB'.
Found device port 'USB' with ID '978441ad-e3d4-4c0e-acbd-b76c31779b76' for transport 'Usb'.
Starting device deployment.
Attempting to connect to device 'USB:SYZ2': iteration 0.
Opening port '\\?\usb#vid_1b9f&pid_5012#7&385755f7&0&4#{c13bcfe9-5e84-4187-9baa-45597ffcbb6f}'.
Attaching debugger engine.
Debugger engine attached.
Generating device specific assemblies.
	- WakeUp Tests v1.0.0.0 with size 1,132 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\WakeUp Tests.pe'.
	- AtlantisDevelopment.TinyCLR.Core v2024.4.19.38631 with size 21,340 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\AtlantisDevelopment.TinyCLR.Core.pe'.
	- AtlantisDevelopment.TinyCLR.GNSS v2024.4.19.38631 with size 15,960 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\AtlantisDevelopment.TinyCLR.GNSS.pe'.
	- AtlantisDevelopment.TinyCLR.SDCardDriver v2024.3.23.38631 with size 26,716 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\AtlantisDevelopment.TinyCLR.SDCardDriver.pe'.
	- mscorlib v2.2.2.1000 with size 72,556 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\mscorlib.pe'.
	- Syzydyne.ChassisTracker v2024.7.25.17362 with size 183,220 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\Syzydyne.ChassisTracker.pe'.
	- GHIElectronics.TinyCLR.Devices.Gpio v2.2.2.1000 with size 4,880 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Gpio.pe'.
	- GHIElectronics.TinyCLR.Devices.I2c v2.2.2.1000 with size 10,464 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.I2c.pe'.
	- GHIElectronics.TinyCLR.Devices.Rtc v2.2.2.1000 with size 3,316 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Rtc.pe'.
	- GHIElectronics.TinyCLR.Devices.Spi v2.2.2.1000 with size 6,284 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Spi.pe'.
	- GHIElectronics.TinyCLR.Devices.Storage v2.2.2.1000 with size 3,432 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Storage.pe'.
	- GHIElectronics.TinyCLR.Devices.Uart v2.2.2.1000 with size 8,012 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Uart.pe'.
	- GHIElectronics.TinyCLR.Devices.Watchdog v2.2.2.1000 with size 1,652 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.Watchdog.pe'.
	- GHIElectronics.TinyCLR.IO v2.2.2.1000 with size 21,144 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.IO.pe'.
	- GHIElectronics.TinyCLR.IO.TinyFileSystem v2.2.2.1000 with size 16,372 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.IO.TinyFileSystem.pe'.
	- GHIElectronics.TinyCLR.Native v2.2.2.1000 with size 6,200 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Native.pe'.
	- GHIElectronics.TinyCLR.Networking v2.2.2.1000 with size 13,072 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Networking.pe'.
	- GHIElectronics.TinyCLR.Update v2.2.2.1000 with size 4,440 bytes at 'E:\Projects\Mobile PC Manager\ChassisTracking\PCB-E Prototype\WakeUp Tests\bin\Debug\pe\GHIElectronics.TinyCLR.Update.pe'.
Total deployment size is 420,192 bytes.
Incrementally deploying assemblies to the device:
Allocating assemblies:
	- Address: 0x08047000 => Syzydyne.ChassisTracker 
	- Address: 0x90A00000 => mscorlib 
	- Address: 0x08073BB4 => AtlantisDevelopment.TinyCLR.SDCardDriver 
	- Address: 0x90A11B6C => AtlantisDevelopment.TinyCLR.Core 
	- Address: 0x90A16EC8 => GHIElectronics.TinyCLR.IO 
	- Address: 0x90A1C160 => GHIElectronics.TinyCLR.IO.TinyFileSystem 
	- Address: 0x90A20154 => AtlantisDevelopment.TinyCLR.GNSS 
	- Address: 0x0807A410 => GHIElectronics.TinyCLR.Networking 
	- Address: 0x90A23FAC => GHIElectronics.TinyCLR.Devices.I2c 
	- Address: 0x90A2688C => GHIElectronics.TinyCLR.Devices.Uart 
	- Address: 0x90A287D8 => GHIElectronics.TinyCLR.Devices.Spi 
	- Address: 0x90A2A064 => GHIElectronics.TinyCLR.Native 
	- Address: 0x90A2B89C => GHIElectronics.TinyCLR.Devices.Gpio 
	- Address: 0x90A2CBAC => GHIElectronics.TinyCLR.Update 
	- Address: 0x90A2DD04 => GHIElectronics.TinyCLR.Devices.Storage 
	- Address: 0x90A2EA6C => GHIElectronics.TinyCLR.Devices.Rtc 
	- Address: 0x90A2F760 => GHIElectronics.TinyCLR.Devices.Watchdog 
	- Address: 0x90A2FDD4 => WakeUp Tests 
Deploying assemblies:
	- Writing sector 1 (2,048 bytes).
	- Writing sector 2 (2,048 bytes).
	- Writing sector 3 (2,048 bytes).
	- Writing sector 4 (2,048 bytes).
	- Writing sector 5 (2,048 bytes).
	- Checking status: sector 6, address @0x08049800...
	- Checking status: sector 6, address @0x08049800...
	- Checking status: sector 6, address @0x08049800...
	- Checking status: sector 6, address @0x08049800...
	- Writing sector 6 (2,048 bytes).
	- Writing sector 7 (2,048 bytes).
	- Writing sector 8 (2,048 bytes).
	- Writing sector 9 (2,048 bytes).
	- Writing sector 10 (2,048 bytes).
	- Checking status: sector 11, address @0x0804C000...
	- Checking status: sector 11, address @0x0804C000...
	- Checking status: sector 11, address @0x0804C000...
	- Checking status: sector 11, address @0x0804C000...
	- Checking status: sector 11, address @0x0804C000...
FAILED to get status device memory @0x0804C000
Assemblies not successfully deployed to the device.
Deployment to the device was not successful.

Dat_Tran · August 6, 2024, 12:56pm

Unfortunately I was able to reproduce on SC20xxx only, relates to cache issue between sd ram and external flash.

On SC13 there is no cache and seems work fine to me. Not sure how to reproduce on sc13xxx yet

Tested on win11 - i9 12900K