pycom pymakr fails to work with visual studio code on macos catalina

PyMakr terminal failure to execute

I’m working with Pycom ( https://pycom.io/ ) IoT devices. One of the tools they supply to work with their devices is a plugin named PyMakr. They have release a version for Visual Studio Code and Atom. The version for VS Code has never worked on my MacBook Pro 15″ or 16″. As a consequence I’ve turned to Atom just to run the plugin. It seems to work properly with Atom. But I’d rather have it work with VS Code, since I do everything else with VS Code.

Here is the setup for the software environment.

  • macOS Catalina, version 10.15.6
  • Visual Studio Code, version 1.49.2
  • PyMakr, version 1.1.7
  • Node.js, version 14.12.0 (installed via Homebrew)

I’ve gone through all the recommended solutions that others say they’ve discovered, and none of them work for me. I’ve seen such error messages in the past on Unix/Linux systems and fixed those error messages in fairly short order. The biggest source is usually a bad shebang at the top of the script. Fix that, and those error messages disappear. But the JavaScript file has no execute bit set, and it appears from the other error messages that node is being used directly instead of invoked within the script itself. The path to the file, and the filename, are all correct.

To make this even more maddening, I have the same setup on a 2012 Mac Mini Server running the same software listed above, and it works. But when it comes to running on my MacBook Pro 15″ or newer 16″, it won’t work at all.

installing visual studio code on debian buster and the raspberry pi 4 model b rev 1.4

A long winded title to announce that I’ve managed to create a deb file from Visual Studio Code source, and to install it on the Raspberry Pi 4 8GiB running Debian Buster 64-bit compiled for arm64.

The deb file was built on the Jetson Xavier NX board, then copied to a thumb drive, then moved over via the thumb drive over to the Rasbperry Pi and installed from there. So far it’s behaved reasonably well. I’ve learned quite a bit about the build tools that come with the source. I suppose it’s good that I found some of the directions I did on the web, but now that I’ve gone through this whole process a number of times, what I used to start with short circuits what is available in the source tree cloned from GitHub.

I appreciate that I can use the Jetson NX as a build system. I also appreciate that there is a method in the source tree for building the deb file. That to me is super. Now I can keep up with releases, knowing I can target 64-bit ARM binaries for Debian/Ubuntu.

And speaking of Debian, the 64-bit OS running on the Raspberry Pi now identifies itself simply as Debian.

Once I feel comfortable running the full build suite in Visual Studio Code I’ll post a streamlined how-to for ARMv8/aarch64/arm64. Too many labels, frankly.