HomeACcessoryKid / ESP8266-HomeKit-Demo

User part of the ESP8266-HomeKit foundation
https://www.youtube.com/watch?v=Xnr-utWDIR8
Apache License 2.0
125 stars 27 forks source link

ls: cannot access '../../bin/eagle.[if]*': No such file or directory #26

Closed supersjimmie closed 6 years ago

supersjimmie commented 6 years ago

I get:

Generate eagle.flash.bin and eagle.irom0text.bin successully in BIN_PATH
eagle.flash.bin-------->0x00000
eagle.irom0text.bin---->0x20000
!!!
Thu Sep 21 10:13:48 DST 2017
ls: cannot access '../../bin/eagle.[if]*': No such file or directory
../../../esptool/esptool.py --baud 230400 -p /dev/cu.usbserial-AH02MF3H write_flash 0x00000 ../../bin/eagle.flash.bin 0x14000 ../../bin/eagle.irom0text.bin

Is that ls: cannot access '../../bin/eagle.[if]*': No such file or directory cosmetic or an issue?

supersjimmie commented 6 years ago

I guess it had to be ls -l $BIN_PATH/eagle.[if]*? And then for the next line, also with the $BIN_PATH:

echo ../../../esptool/esptool.py --baud 230400 -p /dev/cu.usbserial-AH02MF3H write_flash 0x00000 $BIN_PATH/eagle.flash.bin 0x14000 $BIN_PATH/eagle.irom0text.bin
HomeACcessoryKid commented 6 years ago

I propose you reinstall your development environment from scratch.

It works for everyone except you.

Pay good attention to all the details of the installation instructions.

Good luck, HacK

On 22 Sep 2017, at 12:45, supersjimmie notifications@github.com wrote:

I guess it had to be ls -l $BIN_PATH/eagle.[if]*?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/HomeACcessoryKid/ESP8266-HomeKit-Demo/issues/26#issuecomment-331414532, or mute the thread https://github.com/notifications/unsubscribe-auth/AV0HQs54O9uOMcepKsHXcYm97-osHd3qks5sk4-5gaJpZM4PfB7b.

supersjimmie commented 6 years ago

It all seems to work now (other issues are solved) It's only the last 'ls' that seems incorrect. That ls fails because it ignores the $BIN_PATH variable and goes straight to the hard fixed ../../bin. That works if you have the BIN_PATH in that location, but mine is somewhere else. Thats what using the BIN_PATH fixes, insted oth the hardcoded ../../bin.