Version mismatch software upload

[louisvangeldrop]

During deploying main.ts or Start Debugger I get the following error message:

DEV: ! version mismatch DEV: * Raspberry Pi Pico W v6.0.0; file v6.5.0

Deploy cancelled. Your device firmware (v6.0.0) is outdated (min v6.5.0).

[pelikhan]

Hi Louis,

Our version detection is working :) We need a newer firmware build for the pico. Do you have an ESP32? That one should be up to date.

@mmoskal do you have a recent pico build?

[louisvangeldrop]

Hello Peli, I have just flashed an ESP32-Wroom mcu and it works now. In the debugger the software doesn't stop at the breakpoints. However I can step through the code. Variables are not shown in the debug window.

I also have an ESP32C3 Lilygo TTGO and some ESP32S2 based mcu's. I will try later today.

[pelikhan]

Thanks for reporting! (https://github.com/microsoft/devicescript/issues/219)

[pelikhan]

We are tracking issues with the compiled tools on npm. You might want to try the developer setup for now.

---

From: Louis van Geldrop @.> Sent: Saturday, March 18, 2023 5:08:50 AM To: microsoft/devicescript @.> Cc: Peli de Halleux @.>; Comment @.> Subject: Re: [microsoft/devicescript] Version mismatch software upload (Issue #233)

Hello Peli, I have just flashed an ESP32-Wroom mcu and it works now. In the debugger the software doesn't stop at the breakpoints. However I can step through the code. Variables are not shown in the debug window.

I also have an ESP32C3 Lilygo TTGO and some ESP32S2 based mcu's. I will try later today.

— Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fdevicescript%2Fissues%2F233%23issuecomment-1474831347&data=05%7C01%7Cjhalleux%40microsoft.com%7Cbc6cea04656d4dec313f08db27a988f8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638147381327248480%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=w%2FTqM6r7zfNK8s7UgIM2qwKV8Kw%2FC5K3AKAYiW6nl8Q%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA73QKPMBGWT7QFWSDS7HADW4WQVFANCNFSM6AAAAAAV67AZJ4&data=05%7C01%7Cjhalleux%40microsoft.com%7Cbc6cea04656d4dec313f08db27a988f8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638147381327248480%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NyW2nS%2B9saNs6vLoAMjk0xFsl%2BQ%2F9FK0BYSmVWI5Zgo%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>

[pelikhan]

@louisvangeldrop latest drop seems to have fixed the load issues.

[louisvangeldrop]

I am using the VSCode extension and connect to an ESP32Wroom Wemos board. In the Terminal Output tab I can see that my program works - it connects to my Wifi router and returns the found IP-address. The I loop every second in order to log the IP-address Starting the debugger stops at the first line of the program and I can step through the program using the F10-key. However it doesn't stop at the selected breakpoint when I press the F5 key. In the Terminal tab I get the following error: DEV> USB: second begin DEV> USB: mismatched stop DEV> USB: crc err

[mmoskal]

This looks like a problem with the UART chip on the board. Do you know which UART chip does it use? I actually had good results with CP2102 and CH340.

Also, S2 or C3 (provided they have the USB connected directly) will work better.

I'll try to get the RP2040 building going again soon!

[louisvangeldrop]

The UART driver used is: Silicon Labs CP210x USB to UART Bridge. Maybe there is a problem with baudrate.

[pelikhan]

@mmoskal can we detect or document serial comms issues?

[mmoskal]

@pelikhan yeah, once we know what they are; I don't think we have big enough sample size just yet

[mmoskal]

the rp2040 should be now good to go