EspixelStick v4.X I...
 
Notifications
Clear all

EspixelStick v4.X Install Problem

67 Posts
6 Users
0 Reactions
12.2 K Views
Posts: 49
Topic starter
(@gatoruss)
Trusted Member
Joined: 5 years ago
[#56248]

I have a d1 mini pro (ESP8266) 16M. I have it connected to laptop via usb. I come across a thread in which Matrin Mueller linked the latest version of espixelstick v4 on his google drive ( http://doityourselfchristmas.com/forums/showthread.php?58445-ESPixelsick-4-x-and-sdcard-FPP-settings/page2&highlight=espixelstick ). I down loaded it and tried to run jar install. But when I click the jar file nothing happens. So, I ran it in a bat file ( https://thegeekpage.com/unable-to-run-jar-files-in-windows-10-heres-the-solution/ ). When I run the, the jar file runs an opens the installer. Below are screenshots of the the error messages I received. I ran jar installer with device as espixelstickv3 and Wermos d1 mini. Attached are the logs for each.

Any idea what is wrong

Log:

System Output:

bin/win32/mklittlefs -c fs/ -p 256 -b 8192 -s 2072576 firmware/filesystem.bin
-= Building Filesystem Image =-
bin/win32/mklittlefs -c fs/ -p 256 -b 8192 -s 2072576 firmware/filesystem.bin
/config.json
/UpdRecipe.json
/www/alexa.html.gz
/www/apa102.html.gz
/www/artnet.html.gz
/www/ddp.html.gz
/www/dmx.html.gz
/www/e1_31.html.gz
/www/effects.html.gz
/www/esps.css.gz
/www/esps.js.gz
/www/favicon.ico
/www/fpp_remote.html.gz
/www/gece.html.gz
/www/gs8208.html.gz
/www/index.html.gz
/www/mqtt.html.gz
/www/relay.html.gz
/www/renard.html.gz
/www/serial.html.gz
/www/servo_pca9685.html.gz
/www/tls3001.html.gz
/config.json
/UpdRecipe.json
/www/alexa.html.gz
/www/apa102.html.gz
/www/artnet.html.gz
/www/ddp.html.gz
/www/dmx.html.gz
/www/e1_31.html.gz
/www/effects.html.gz
/www/esps.css.gz
/www/esps.js.gz
/www/favicon.ico
/www/fpp_remote.html.gz
/www/gece.html.gz
/www/gs8208.html.gz
/www/index.html.gz
/www/mqtt.html.gz
/www/relay.html.gz
/www/renard.html.gz
/www/serial.html.gz
/www/servo_pca9685.html.gz
/www/tls3001.html.gz
/www/tm1814.html.gz
/www/ucs1903.html.gz
/www/ucs8903.html.gz
/www/ws2801.html.gz
/www/ws2811.html.gz
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 erase_flash
/www/tm1814.html.gz
/www/ucs1903.html.gz
/www/ucs8903.html.gz
/www/ws2801.html.gz
/www/ws2811.html.gz
Done

-= Erasing ESP Flash =-
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 erase_flash
Done
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 --before default_reset --after hard_reset write_flash 0x0 firmware/esp8266/d1_mini-app.bin 0x200000 firmware/filesystem.bin

-= Uploading Firmware =-
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 --before default_reset --after hard_reset write_flash 0x0 firmware/esp8266/d1_mini-app.bin 0x200000 firmware/filesystem.bin
Done

ESP Action FAILED bin/win32/mklittlefs -c fs/ -p 256 -b 8192 -s 2072576 firmware/filesystem.bin
-= Building Filesystem Image =-
bin/win32/mklittlefs -c fs/ -p 256 -b 8192 -s 2072576 firmware/filesystem.bin
/config.json
/UpdRecipe.json
/www/alexa.html.gz
/www/apa102.html.gz
/www/artnet.html.gz
/www/ddp.html.gz
/www/dmx.html.gz
/www/e1_31.html.gz
/www/effects.html.gz
/www/esps.css.gz
/www/esps.js.gz
/www/favicon.ico
/www/fpp_remote.html.gz
/www/gece.html.gz
/config.json
/UpdRecipe.json
/www/alexa.html.gz
/www/apa102.html.gz
/www/artnet.html.gz
/www/ddp.html.gz
/www/dmx.html.gz
/www/e1_31.html.gz
/www/effects.html.gz
/www/esps.css.gz
/www/gs8208.html.gz
/www/esps.js./www/fpp_remote.html.gz
gz
/www/favicon.ico
/www/gece.html.gz
/www/index.html.gz
/www/mqtt.html.gz
/www/relay.html.gz
/www/renard.html.gz
/www/serial.html.gz
/www/servo_pca9685.html.gz
/www/tls3001.html.gz
/www/tm1814.html.gz
/www/ucs1903.html.gz
/www/gs8208.html.gz
/www/index.html.gz
/www/mqtt.html.gz
/www/relay.html.gz
/www/renard.html.gz
/www/serial.html.gz
/www/servo_pca9685.html.gz
/www/tls3001.html.gz
/www/tm1814.html.gz
/www/ucs1903.html.gz
/www/ucs8903.html.gz
/www/ws2801.html.gz
/www/ws2811.html.gz
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 erase_flash
/www/ucs8903.html.gz
/www/ws2801.html.gz
/www/ws2811.html.gz
Done

-= Erasing ESP Flash =-
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 erase_flash
Done
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 --before default_reset --after hard_reset write_flash 0x0 firmware/esp8266/espsv3-app.bin 0x200000 firmware/filesystem.bin

-= Uploading Firmware =-
bin/win32/python3/python bin/upload.py --chip esp8266 --baud 460800 --port COM4 --before default_reset --after hard_reset write_flash 0x0 firmware/esp8266/espsv3-app.bin 0x200000 firmware/filesystem.bin
Done

ESP Action FAILED

Serial Output:

espi recent 001
espi recent 002

66 Replies
Posts: 49
Topic starter
(@gatoruss)
Trusted Member
Joined: 5 years ago

Following up on my original post, I downloaded Espixelstick v4.4. I was able to install 4.4 and access the device thru the web browser several times, powering via the USB. However, when I tried to power via 5v/gnd pins, the web connection would not establish, and I could no longer access via web when i went back to powering using USB connection -- the device kept trying to connect unsuccessfully. So, I tried to reinstall v4.4 -- that installation was slow and the device kept trying to connect to the to the newtwork unsuccessfully. The serial output eventually says it is connected, but the web browser is not responsive.

I had heard/read that v4.4 had issues, but any idea what I may be doing wrong whem installing Martin's v4.x as described in my original post?


Reply
Posts: 8517
(@angus40)
Illustrious Member
Joined: 15 years ago
gatoruss wrote:Following up on my original post, I downloaded Espixelstick v4.4. I was able to install 4.4 and access the device thru the web browser several times, powering via the USB. However, when I tried to power via 5v/gnd pins, the web connection would not establish, and I could no longer access via web when i went back to powering using USB connection -- the device kept trying to connect unsuccessfully. So, I tried to reinstall v4.4 -- that installation was slow and the device kept trying to connect to the to the newtwork unsuccessfully. The serial output eventually says it is connected, but the web browser is not responsive.

I had heard/read that v4.4 had issues, but any idea what I may be doing wrong whem installing Martin's v4.x as described in my original post?

My guess is the vreg has let the smoke out on the 5v side.
Have you tried powering the mini pro from the 3.3V ?


Reply
MartinMueller2003
Posts: 7614
(@martinmueller2003)
Illustrious Member
Joined: 14 years ago

The error " ESP Action FAILED bin/win32/mklittlefs -c fs/ -p 256 -b 8192 -s 2072576 firmware/filesystem.bin" indicates an issue with the tools that the installer uses or an issue with the device being programed. I suspect an issue with the device.


Reply
Posts: 49
Topic starter
(@gatoruss)
Trusted Member
Joined: 5 years ago
MartinMueller2003 wrote:The error " ESP Action FAILED bin/win32/mklittlefs -c fs/ -p 256 -b 8192 -s 2072576 firmware/filesystem.bin" indicates an issue with the tools that the installer uses or an issue with the device being programed. I suspect an issue with the device.

I tried the installer with 2 other devices (all d1 mini pros with 16M). With the same results as indicated in my first post.

In addition, as note in my first post the jar installer download from your google drive will not open when clicked (hour glass spins for a few seconds, and then nothing). I tried to uninstall and reinstall java, but result was the same. The only way I was able to run the installer was to create a bat file as noted in my original post.


Reply
Page 1 / 14
Share: