Error tool-mkspiffs

Question

Error tool-mkspiffs

joelsernamoreno opened this issue 4 years ago · 32 comments

Hello!

When I try to flash the rfquack firmware with docker I get the following error: Error: Detected unknown package 'tool-mkspiffs'

Can you check this?

Thanks

Answer 1 · 2021-04-03T13:20:00.000Z

Looks new. I suspect it’s due to PlatformIO not finding that package. If you have a PlatformIO installation on the host, can you try to install only that package and see what happens?

…

On 3 Apr 2021, at 14:14, Joel Serna Moreno ***@***.***> wrote: Hello! When I try to flash the rfquack firmware with docker I get the following error: Error: Detected unknown package 'tool-mkspiffs' Can you check this? Thanks — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 2 · 2021-04-03T13:28:01.000Z

Hi!

If I run pio update you can see that tool-mkspiffs is installed correctly:

Platformio includes this package automatically. If you remove this check from the rfquack installation I think this problem will be solved

Answer 3 · 2021-04-03T14:34:01.000Z

I tried flashing RFQuack on my old laptop (it worked here before), but now I get the same error

I think platformio has made some modification and this is not working now

If you remove the tool-mkspiffs installation in rfquack this should work

Answer 4 · 2021-04-03T15:59:35.000Z

To manually install tool-mkspiffs you can run:

platformio platform install espressif32 --with-package tool-mkspiffs

Can you check this in rfquack?

Answer 5 · 2021-04-03T22:31:55.000Z

Can you try to install rfquack on any dongle using Docker?

I would like to know if it is a problem with rfquack, platformio or my computer. We have tried several colleagues and we all get the same error

Thanks

Answer 6 · 2021-04-04T19:13:14.000Z

H!

This works for me:

1.- Create a Dockerfile on your computer with the following content:

2.- Compile this with: docker build -t evilcrowrf/rfquack .

3.- Flash firmware: docker run --device=/dev/ttyUSB0:/board -e BOARD=ESP32 -e RADIOA=CC1101 -e RADIOA_CS=27 -e RADIOA_IRQ=25 -e RADIOB=CC1101 -e RADIOB_CS=5 -e RADIOB_IRQ=2 --rm -it evilcrowrf/rfquack

To fix this for everyone you can update rfquack with this information. Platformio now does not allow to use older versions and therefore rfquack cannot install the necessary packages.

Thanks!

Answer 7 · 2021-04-12T20:43:20.000Z

@joelsernamoreno I'm looking into this, but I don't see tool-mkspiffs used anywhere in the default Dockerfile; if this is something specific to your flavor of Dockerfile, can you make a case why this should be addressed by RFQuack? If it's something blocking that doesn't conflict with RFQuack, I'm more than happy to help.

Answer 8 · 2021-04-12T20:49:27.000Z

Hi!

When you run the command to flash rfquack with docker you are using espressif32. When you install espressif32 on platformio it automatically installs other packets like tool-mkspiffs

The problem is that your Dockerfile uses an old version of platformio and because of this it doesn't work correctly.

Change pip install -U platformio==4.1.0 to pip install -U platformio

Answer 9 · 2021-04-12T21:01:05.000Z

OK. Got it. That's what I'm about to commit. Thanks!

Answer 10 · 2021-04-12T21:03:38.000Z

It seems that now platformio does not work properly if you are using older versions.

Let me know when you change this and I'll test it :D

Answer 11 · 2021-04-12T21:10:46.000Z

Have a look now @joelsernamoreno and let me know if it builds fine.

Answer 12 · 2021-04-12T21:15:51.000Z

Hi!

I keep getting the same error

Have you changed this in the public container? Note that my installation is with docker run:

docker run --device=/dev/ttyUSB0:/board -e BOARD=ESP32 -e RADIOA=CC1101 -e RADIOA_CS=27 -e RADIOA_IRQ=25 -e RADIOB=CC1101 -e RADIOB_CS=5 -e RADIOB_IRQ=2 --rm -it rfquack/rfquack

I am not flashing this locally

Answer 13 · 2021-04-12T21:26:23.000Z

No. I only changed the Dockerfile. Just run make docker-build to have a fresh image built locally.

Answer 14 · 2021-04-12T21:47:40.000Z

Well, this has compiled

How do I flash this now? I have installed the following:

docker run --device=/dev/ttyUSB0:/board -e BOARD=ESP32 -e RADIOA=CC1101 -e RADIOA_CS=27 -e RADIOA_IRQ=25 -e RADIOB=CC1101 -e RADIOB_CS=5 -e RADIOB_IRQ=2 --rm -it rfquack/rfquack:latest

Now I don't get errors from tool.mkspiffs, but I get these errors:

Answer 15 · 2021-04-12T22:02:57.000Z

these compilation errors look familiar to me, that's why I was using @FiorixF1 git repos.
it seems to me that there is some misalignment between RadioLib and RFQuack,
but if @phretor manages to compile the error should be on my side, somewhere...

strange, using the latest Docker hub RFQuack image, I still get:

[dirk@t520 RFQuack]$ docker run --device /dev/ttyUSB0:/board -e BOARD=ESP32    -e RADIOA=CC1101 -e RADIOA_CS=5  -e RADIOA_IRQ=4  -l DEBUG --rm -it rfquack/rfquack:latest
Installation ID is 9b58cd12-5225-4f74-8097-14f3d1f0999f
Processing ESP32 (platform: espressif32; board: esp32doit-devkit-v1; framework: arduino)
---------------------------------------------------------------------------------------------------------------------------------------------
PackageManager: Installing tool-mkspiffs @ ~2.230.0
Error: Detected unknown package 'tool-mkspiffs'

Answer 16 · 2021-04-12T22:03:01.000Z

Lol, now my previous solution doesn't work either

Seems to have broken everything :(

Answer 17 · 2021-04-12T22:05:13.000Z

Hi @dgeppert

With the solution I had written before (create a new Dockerfile with the information I attached) the tool-mkspiffs problem was solved

But... after today's new changes it seems to have broken everything.

Answer 18 · 2021-04-12T22:05:17.000Z

in my Dockerfile I successfully use:

RUN apt-get update \
  && apt-get install -y --no-install-recommends git wget unzip make \
  && apt-get purge -y --auto-remove \
  && rm -rf /var/lib/apt/lists/* \
  && pip install -U platformio \
  && platformio platform install espressif32 --with-package tool-mkspiffs \
  && pip install j2cli \
  && pip install google==2.0.3 \
  && pip install protobuf==3.11.3

hth

Answer 19 · 2021-04-12T22:06:43.000Z

@FiorixF1 could you please send PRs from your RadioLib fork to rfquack/RadioLib so I can realign?

Answer 20 · 2021-04-12T22:10:16.000Z

@dgeppert
Using your dockerfile I keep getting the RadioLib error

Answer 21 · 2021-04-12T22:13:57.000Z

hi @joelsernamoreno
with the changes in Dockerfile only the mkspiffs issue was addressed according to your previous proposal

maybe a stupid add: the Dockerfile is not used for docker run which pulls the hub image already compiled with the submitter's Dockerfile , only for docker build

compilation issues will be solved once @phretor incorporates @FiorixF1 RadioLib changes and aligns RFQuack, I guess...

Answer 22 · 2021-04-12T22:18:46.000Z

Oh, good. This is a radiolib problem

Sorry for trying to update this. A few weeks ago I started getting the tool-mkspiff error.

I solved this by creating an updated Dockerfile to use the latest version of platformio and this worked.

I didn't think this problem would become so big now hahaha

Answer 23 · 2021-04-12T22:47:46.000Z

last comment: after rm all my docker images/containers a docker run rfquack/rfquack:latest does not show the mkspiffs error message. seems it did not pull the new image and reused the local one ;-(

just the RadioLib compilation errors remain as @joelsernamoreno already reported

Answer 24 · 2021-04-13T09:39:27.000Z

@dgeppert @joelsernamoreno see the latest commits (and, in particular, the Makefile and newer Dockerfile) and additions to the README.md file and let me know if you're still having issues.

In short, you should be able to:

$ edit build.env
$ make docker-build
$ make build
$ PORT=/dev/ttyUSB0 make flash

Answer 25 · 2021-04-13T10:10:11.000Z

Hello!

In the make build command I get the following errors:

Answer 26 · 2021-04-13T10:35:39.000Z

Check now please:

$ make docker-build-nc && make build

...

Compiling .pio/build/HUZZAH32/FrameworkArduino/esp32-hal-timer.c.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/esp32-hal-touch.c.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/esp32-hal-uart.c.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/libb64/cdecode.c.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/libb64/cencode.c.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/main.cpp.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/stdlib_noniso.c.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/wiring_pulse.c.o
Compiling .pio/build/HUZZAH32/FrameworkArduino/wiring_shift.c.o
Archiving .pio/build/HUZZAH32/libFrameworkArduino.a
Linking .pio/build/HUZZAH32/firmware.elf
Retrieving maximum program size .pio/build/HUZZAH32/firmware.elf
Checking size .pio/build/HUZZAH32/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM:   [==        ]  16.9% (used 55344 bytes from 327680 bytes)
Flash: [==        ]  22.9% (used 299594 bytes from 1310720 bytes)
Building .pio/build/HUZZAH32/firmware.bin
esptool.py v3.0
=============================== [SUCCESS] Took 33.12 seconds ===============================

Answer 27 · 2021-04-13T10:54:11.000Z

Hi!

It compiles now, but I can't connect to the dongle:

This happens when running the command docker run --device /dev/ttyUSB0 --rm -it rfquack/cli tty -P /dev/ttyUSB0

I get the error ModuleNotFoundError: No module named 'click' but this is installed on my machine

Answer 28 · 2021-04-13T12:29:55.000Z

I have tried to install RFQuack-cli locally, but there are ipython errors:

git clone https://github.com/rfquack/RFQuack-cli.git
cd RFQuack-cli/
pipenv install -e .

Answer 29 · 2021-04-13T13:58:11.000Z

There was indeed a missing line in the Dockerfile: thanks for your patience.

When installing locally, beware that you're using Python < 3.9 (which is the recommended minimum version). Because of that, IPython could not be installed.

I recommend using Pyenv to manage multiple Python versions on the same system, if you really want to go dockerless for this one.

Answer 30 · 2021-04-13T13:58:36.000Z

Closing this issue. If the CLI thing reappears, please open an issue at rfquack/RFQuack-cli.

Answer 31 · 2021-04-13T14:49:12.000Z

Hi!

This work:

cd RFQuack-cli
make docker-build
docker run --device /dev/ttyUSB0 --rm -it rfquack/cli:latest tty -P /dev/ttyUSB0

Thanks!

Answer 32 · 2021-04-13T14:51:33.000Z

Great! And by now you can avoid make docker-build and simply use pre-built images from Docker Hub. In practice: simply skip 2. and go straight to 3.