VS Arduino - Print Page

VS Arduino
Visual Micro >> Installation & Troubleshooting >> Raspberry pi Pico https://www.visualmicro.com/forums/YaBB.pl?num=1631818335 Message started by Precious Roy on Sep 16^th, 2021 at 6:52pm

Title: Raspberry pi Pico
Post by Precious Roy on Sep 16^th, 2021 at 6:52pm

Hi,

I have been having some issues with programming my pi pico board. The short version is, if VS2019 is set to debug it works fine but when set to release i cant connect to the serial port and it says its busy in the arduino ide as well as in VS. but if i programm the same code with the arduino ide it works just fine(also in VS) even afeter i reset it it still does not work unless

i was hoping one of you has this issue.

I am using the pi board data you can download from the manager
https://github.com/earlephilhower/arduino-pico
And I have all my settings set to default in the arduino ide and i uploaded the example->basic->AnalogueReadSerial

its all basic stuff so i was hoping one of you had a fix for me

Title: Re: Raspberry pi Pico
Post by Simon@Visual Micro on Sep 17^th, 2021 at 11:14am

Thanks for the report.

Can you attach the full build output as a txt file, with the verbose and show build properties Enabled (shown at top of this page), so we can ensure we have all settings correct to replicate the issue?

Title: Re: Raspberry pi Pico
Post by Precious Roy on Sep 17^th, 2021 at 12:37pm

i dont mind, but i dont see an attachment button.

Edit:
https://dir.nu/61448f904f00b

you should be able to download it from that link

Title: Re: Raspberry pi Pico
Post by Simon@Visual Micro on Sep 17^th, 2021 at 1:39pm

Thanks for the logs.

Are you using the same board in both IDE's, as it appears in Arduino IDE it is using the 1.9.4 Core from the link provided, but in vMicro it is using the 2.4.1 core from the mbed_nano package?

The attachment button should be visible below the box you add your reply in, and if it is not there, there should be an Update Session button on the toolbar at the top which will validate your password and once updated the [Choose File] button should appear.

Do you have the vMicro > Upload > Auto-Open Serial Monitor option enabled? (if so disable this, and try to manually connect)

Can you also attach a picture of the Serial monitor, from Visual Micro when it fails to connect (with it wide enough to see all the buttons at the bottom of the monitor)?

Title: Re: Raspberry pi Pico
Post by Precious Roy on Sep 17^th, 2021 at 4:26pm

Well as you can see in the image i am clicking on the 1.9.4 version but they have the same name so i do not know if this can cause an issue.

and now i see the attachment button, weird that it was not there.

Untitled_014.png ( 26 KB | 2 Downloads )

Title: Re: Raspberry pi Pico
Post by Precious Roy on Sep 17^th, 2021 at 4:28pm

i just noticed something. sometimes after uploading the new program (Where it was working before programed from arduino) when the comport is 7 it makes a new one and calls it 8. but i can not connect on ether of them.

but when i program with arduino it is always 7 and never changes.

2_010.png ( 30 KB | 4 Downloads )

Title: Re: Raspberry pi Pico
Post by Simon@Visual Micro on Sep 17^th, 2021 at 6:04pm

Thanks for the detail.

Can you un-install the Mbed_rp2040 core, and then restart Visual Studio, to see if this improves the situation?

Title: Re: Raspberry pi Pico
Post by Precious Roy on Sep 18^th, 2021 at 9:28am

Ok that did fix the issue, so it seems to have an issue with the name. and it choosing the wrong core even if the right one is selected. still its a weird issue boteh cores work fine in the arduino ide.

thanks for the help.

Title: Re: Raspberry pi Pico
Post by Tim@Visual Micro on Sep 18^th, 2021 at 3:13pm

Great, we have some changes coming shortly that will resolve multple cores, beta cores and also support multiple versions of the same core.

The switching to a different port is intentional for some cores. Some cores enter programming mode on a different port and include an instruction to let Visual Micro know that is required. The other core works that way. I think the board incorrectly remained on the programming port because of the confusion between cores.

Thanks for the update.