uploadProject command fails with rmdir OSError: no such file or directory: 'null'

[dajtxx]

I have installed pymakr in VSCode on MacOS. I can talk to the fipy via screen, or the terminal in VS code, started from the pymakr plugin.

When I try to upload the sample project I get this error:

pymakr.conf has this content:

{
    "name": "Led Example"
}

[jakobrosenberg]

Hi @dajtxx . Could I ask you to post a screenshot of your device info? You can get it by hovering over your device.

Example

On windows VSCode can't be active when you hover over it or the overlay will disappear when you click win+shift+s (screenshot shortcut). I don't know if it behaves the same on Macs, but rather be safe than sorry. 🙂 

[dajtxx]

Hi @jakobrosenberg , here it is. I cannot connect to it to get better info.

Also, here is what shows in the terminal after pressing the boot button:

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff8020,len:8
load:0x3fff8028,len:2128
load:0x4009fa00,len:19760
entry 0x400a05bc

[jakobrosenberg]

Judging from the overlay, it seems Pymakr hasn't had write access to the terminal of your device. If you click ctrl + f in the terminal, does that give you a >>>?

Also, does the hover overlay give you the same info if you connect the device first?

[dajtxx]

Here is what I see using a fipy that allows me to connect to the REPL:

You can see even with this one, that is connected, I can't get whatever details would show under Project or System. But I can talk to it via vscode terminal.

The bad one just never got to the REPL.

I have now been able to download older firmware to the bad one and it's talking again. It is interesting this one with the oldest firmware I could get from the update tool shows more info in the vscode popup than the unchanged fipy.

[dajtxx]

I still cannot get the upload project command to work reliably on macos, even though the dev has perms 0666. sudo code . makes no difference either.

It seems to be more reliable on Windows, but even then not completely.

I flashed back to a legacy firmware because I have no interest in pybytes and it seemed to want to connect to pybytes upon boot after a failed upload.

[jakobrosenberg]

If you can't access to the REPL at all, you can try flashing the firmware with the Erase during update checked. If you still can't access the REPL after erasing the device, I suspect your device may be faulty.

For clarification, Pymakr can only communicate with your device through the REPL, so this has to be fixed before anything else.