mbed v1.2.2 - Portenta Not Recognized

[jwestmoreland]

Hello,

Is there an update to this:

[https://gist.githubusercontent.com/per1234/e49b8ff532b1617d880a9f08298cada9/raw/b57d7c97f788344a569afedc730439ec81375a0f/package_portentaworkaround_index.json

The 1.2.2 download installed - 1.8.13 ok but Pro-IDE doesn't recognize the Portenta using the above that worked with 1.2.1.

Thanks,
John

[per1234]

Hi @jwestmoreland. Unfortunately, the workaround breaks on every release of the Arduino mbed-Enabled Boards platform.

Here's the new Boards Manager URL:
https://gist.githubusercontent.com/per1234/e49b8ff532b1617d880a9f08298cada9/raw/af4158932e1537bc90bbc5c741340765eeb2c2c4/package_portentaworkaround_index.json

Just replace the previous one in your File > Settings > Open CLI Configuration, wait until you see the popup notification "The CLI configuration has been successfully reloaded", then restart the Pro IDE.

After that, the Portenta should again be recognized. I'll get the other instructions about this workaround updated with the new URL.

If you still have a problem, let me know and I'll help you out.

[ubidefeo]

@jwestmoreland
bear with us, we're close to releasing an update to the alpha IDE that will handle this annoyance once and for all.
it's a matter of days now.
As development moves forward we'll have a more defined release schedule :)

[jwestmoreland]

@per1234 and @ubidefeo ,

pert & Ubi - Thank you both for the quick response! Looking forward to the new alpha IDE release too!

Best Regards,
John W.

[jwestmoreland]

@per1234 ,

I'm getting an error - please see the below:
Error: Request getBoardDetails failed with message: 13 INTERNAL:
Failed to parse server response

Regards,
John W.

[per1234]

Hi @jwestmoreland sorry for the slow response. I don't know what could be the cause of this

Request getBoardDetails failed with message: 13 INTERNAL: Failed to parse server response

error. I don't have any problems when using my Portenta with the Pro IDE and the workaround package index URL.

Do you have any other Arduino boards? If so, do you get the same error when you use them with the Pro IDE?

[jwestmoreland]

pert,

Just tried with the Nano IoT and it does the same thing.

I used to work with a bunch of guys that would say "works for you and not for me" - I guess that's the case.

Due to what was added to #295 I thought I had to wait for 0.0.7 - guess I'm glad I asked now.

So, suggestions? I'm definitely using this:
[https://gist.githubusercontent.com/per1234/e49b8ff532b1617d880a9f08298cada9/raw/af4158932e1537bc90bbc5c741340765eeb2c2c4/package_portentaworkaround_index.json]

Regards,
John
PS - The last nightly build of the CLI recognized the Portenta H7 with no problem - if that is an interesting data point or not. And of course 1.8.13 works fine as long as I change ./arduinobeta/ back to ./arduino-beta/.

[per1234]

What happens if you run this Arduino CLI command with any of the boards connected to your computer:

arduino-cli board list

I am suspicious this error happens when Arduino CLI attempts to contact the builder.arduino.cc API to try to auto-detect the board based on its VID/PID pair:
https://github.com/arduino/arduino-cli/blob/0.11.0/commands/board/list.go#L38

[jwestmoreland]

C:\tmp>arduino-cli board list
Port Type Board Name FQBN Core
COM11 Serial Port (USB) Unknown
COM12 Serial Port (USB) Unknown
COM16 Serial Port (USB) Unknown
COM17 Serial Port (USB) Unknown
COM22 Serial Port (USB) Unknown
COM23 Serial Port (USB) Arduino NANO 33 IoT arduino:samd:nano_33_iot arduino:samd
COM4 Serial Port (USB) Arduino Portenta H7 (M7 core) arduino-beta:mbed:envie_m7 arduino-beta:mbed
COM5 Serial Port (USB) Unknown
COM6 Serial Port (USB) Unknown
COM7 Serial Port (USB) Unknown

@per1234 - is the (suspected) error a bug in the CLI bug list?

[jwestmoreland]

Pert,

Update:

I also checked my routers and firewalls just to see if something was going on there - but nothing showed up regarding this issue.

But, I did find this:

M$ Defender had been blocking network access of arduino-cli.exe - it allowed access for the one in my path which was not the same as the one for the Pro IDE.

I have since fixed that - I thought - but I will probably either try to disable defender completely or uninstall it now to see if I can get the problem resolved.

I had no idea that defender was even blocking access for this app at all. I have other virus scan/firewall tools that I thought were in sole control - but seems M$ feature creep is omnipresent.

Regards,
John

[jwestmoreland]

Pert,

Well, this just keeps getting interesting.

I thought I had disabled M$ Defender - note, with the new Win10 2020 Updates - the normal 'google foo' on how to do that doesn't apply - things are a little 'new' after some of the updates - I got the following:

But, after moving off the install of 0.0.6 and reinstalling into a new directory - it appears the problem isn't occurring anymore. I guess once the new M$ Defender decides to latch-on to a file - it's hard to shake it - I don't have any other explanation now. Wireshark doesn't show anything when the file can't run.

Regards,
John
PS - Took the pic after I added 2nd checkmark.

[jwestmoreland]

@jwestmoreland
bear with us, we're close to releasing an update to the alpha IDE that will handle this annoyance once and for all.
it's a matter of days now.
As development moves forward we'll have a more defined release schedule :)

Hmmm, matter of days....

[ubidefeo]

@jwestmoreland
I know, I know.
We bumped into a few show-stoppers and to be honest a release like that would have upset a lot of users.
We prefer to get a snarky (deserved/appreciated) comment like yours than release something that won't make us happy.
Suffice it to say we have already written the release notes ;)