-
Notifications
You must be signed in to change notification settings - Fork 727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP8266-01s with CH340G USB - ESP Link does not provide an AP for configuration #543
Comments
First check my builds of 3.2.x version, they are available in other issues |
But first try this: |
same behavior with both tries. |
@msmthng do you have serial log ? |
how i can collect the serial log?
Am So., 27. Feb. 2022 um 18:33 Uhr schrieb Bartłomiej Zimoń <
***@***.***>:
… @msmthng <https://github.com/msmthng> do you have serial log ?
—
Reply to this email directly, view it on GitHub
<#543 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJTHNBMNIJ24I5SLHHI4I7LU5JN5DANCNFSM5PNXIBXA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Use terminal application like putty with log to file feature enabled. |
You can write to me on gitter.im |
logoutput: = any setting to change in addition (beside comport, baudrate 1152000)? |
115200,230400, text should be visible there |
I have the same problem w/ and ESP-12 and tried several of the 3.2 releases. It looks like the flash worked, the LED blinks about 1/second but there is no ESP-xxx AP to connect to. I tried two different NodeMCUs - same result. I loaded the Example skets that sets up an AP on the ESP8266 and was able to connect to it so I think the WiFi circuitry and antenna is OK. I tried getting a log at 115200 and have garbled outputs much like the earlier example. So, a couple of questions: o Is there a way to connect esp-link to my WiFi network without connecting to the not-visible esp-link AP? o What can I do to get a better log? The putty display shows very quick lines of text which I can't read and can't be logged successfully at 115200. There are some text characters but not enough to make sense of. small sample: o What else can I try? |
@profroyk The bootloader messages are sent at a baud rate of 74880. Try to receive the boot log at that rate to read it. |
Thanks. That did the trick for logging. It's the same error over and over.
2nd boot version : 1.6
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size & Map: 4Mbit(256KB+256KB)
no GPIO select!
jump to run user1 @ 1000
rf_cal[0] !=0x05,is 0xFF
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8
I am using a HiLetgo ESP-12 NodeMCU w/ the NodeMCu pinout. There is a
green LED blinking about 1/second which I figured was the WiFi status LED
so I didn't pull it up or hook an LED in. There is no yellow Serial
activity LED. blinking that I can see.
I used the ExpressIf flashing utility and when it finished the status box
was Green and the log said everything PASSED, but I'm wondering whether
the programming actually worked. This is in the Download box:
AP: 42-91-51-44-E7-23 STA: 40-91-51-44-E7-23
Which GPIO is the Select and what should I do with it? Does it matter?
From the log (and I'm guessing) the jump to the start of user1.bin (0x1000)
isn't working and rf_cal[]0 looks like it was looking for a value other
than 0xFF . I did not add any resistors to the GPIO's. Should I have?
I feel like I should be able to figure this out myself but I've been
Googling for several hours and nothing pans out.
Thanks
Roy
…On Tue, Apr 5, 2022 at 2:37 AM yesyesuk ***@***.***> wrote:
@profroyk <https://github.com/profroyk> The bootloader messages are sent
at a baud rate of 74880. Try to receive the boot log at that rate to read
it.
—
Reply to this email directly, view it on GitHub
<#543 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZF7J5RUKDT2C6NGG2D6TDVDQCVPANCNFSM5PNXIBXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
|
Please you try to flash blank.bin at 0x80000 please find my latest builds in other issues |
I'll try it when I get home tonight but are those addresses correct? They
are both the same address so wouldn't esp_init_data_default overwrite
blank.bin?
Roy
…On Tue, Apr 5, 2022 at 2:52 PM Bartłomiej Zimoń ***@***.***> wrote:
did you tries to flash blank.bin at 0x80000
and next esp_init_data_default.bin 0x80000
—
Reply to this email directly, view it on GitHub
<#543 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZF7J7X3HTMX4XV6QDNLG3VDSYZ7ANCNFSM5PNXIBXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
|
blank.bin is to erase data and esp_init_data_defaults is to init this memory with defaults. |
Thanks. I put the esp_init_data_defaults at 0x80000. It didn't make any
difference - Same problem. Here's a snippet of the console log:
2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 4Mbit(256KB+256KB)
no GPIO select!
jump to run user1 @ 1000
rf_cal[0] !=0x05,is 0xFF
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8
I think I may know what's happening but I don't know what to do about it.
I tried running esptool to do the flashing instead of the ExpressIf utility
and got an error when trying to write user1.bin:
C:\Users\roykr\psuproj\esp-link\esptool>python esptool --port COM7 --baud
11520 write_flash --flash_freq 20m --flash_mode qio --flash_size 32m 0x1000
user1.bin 0x0000 boot_v1.6.bin 0x3fc000 esp_init_data_default.bin 0x3fe000
blank.bin
WARNING: Flash size arguments in megabits like '32m' are deprecated.
Please use the equivalent size '4MB'.
Megabit arguments may be removed in a future release.
esptool.py v3.2
Serial port COM7
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying
again...
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
WARNING: Detected crystal freq 20.89MHz is quite different to normalized
freq 26MHz. Unsupported crystal in use?
Crystal is 26MHz
MAC: 58:bf:25:d9:e6:e9
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00051fff...
Flash will be erased from 0x00000000 to 0x00000fff...
Flash will be erased from 0x003fc000 to 0x003fcfff...
Flash will be erased from 0x003fe000 to 0x003fefff...
Compressed 330756 bytes to 244619...
Writing at 0x00001000... (6 %)Traceback (most recent call last):
File "C:\Program
Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.3312.0_x64__qbz5n2kfra8p0\lib\runpy.py",
line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Program
Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.3312.0_x64__qbz5n2kfra8p0\lib\runpy.py",
line 87, in _run_code
exec(code, run_globals)
File "C:\Users\roykr\psuproj\esp-link\esptool\esptool\__main__.py", line
11, in <module>
esptool._main()
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 5136, in _main
main()
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 4602, in main
operation_func(esp, args)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 3873, in write_flash
esp.flash_defl_block(block, seq, timeout=timeout)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 154, in inner
return func(*args, **kwargs)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 918, in flash_defl_block
self.check_command("write compressed data to flash after seq %d" % seq,
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 495, in check_command
val, data = self.command(op, data, chk, timeout=timeout)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 458, in command
self.write(pkt)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 421, in write
self._port.write(buf)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\serial\serialwin32.py",
line 325, in write
raise SerialTimeoutException('Write timeout')
serial.serialutil.SerialTimeoutException: Write timeout
Apparently esptool had trouble writing to that segment. I tried this on
several NodeMCU's and got the same failure. I tried writing all of the
other segments and that worked. The only write that failed was the one to
user1.bin. I tried writing user2.bin and had the same problem. The write
always hangs up 6% of the way in.
o Can you think of a reason why this would be happening? Have you seen
this before?
o Can I put user1.bin somewhere else in the flash?
Thanks
Roy
…On Wed, Apr 6, 2022 at 8:43 AM Bartłomiej Zimoń ***@***.***> wrote:
blank.bin is to erase data and esp_init_data_defaults is to init this
memory with defaults.
—
Reply to this email directly, view it on GitHub
<#543 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZF7J24ZHY4ROZ777FRJX3VDWWJZANCNFSM5PNXIBXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
|
Breakthrough.
I flashed user2.bin to 81000 and esp-link was able to boot to user2.bin. I
can connect to the ESP_DE9E00B network (but not every time) but now I'm
running into configuration problems.
Scanning for networks doesn't return anything and when I enter my SSID and
p/w I get a message saying message saying Error Switching Networks.
Here's the log from putty after a bunch of garbage characters which I
assume is from reset.
121> ** esp-link v3.0.14-g963ffbb
121> Flash config restore *FAILED*
121> CONN led=0
122> SER led=14
124> Wifi init, mode=AP+STA
126> Wifi uses DHCP, hostname=esp-link
130> "ip": "0.0.0.0"
132> "netmask": "0.0.0.0"
134> "gateway": "0.0.0.0"
137> "hostname": "esp-link"
140> sleep enable,type: 2
143> Httpd init, conn=0x3fff3820
146> No user file system found!
149> Serbridge pins: reset=12 isp=13 swap=0
162> Reset cause: 6=external
162> exccause=0 epc1=0x0 epc2=0x0 epc3=0x0 excvaddr=0x0 depc=0x0
162> Flash map 4MB:512/512, manuf 0x20 chip 0x4016
167> ** esp-link v3.0.14-g963ffbb: ready, heap=21368
172> SNTP timesource set to us.pool.ntp.org with offset 0
177> initializing user application
180> Waiting for work to do...
183> mode : sta(58:bf:25:d9:e0:0b) + softAP(5a:bf:25:d9:e0:0b)
189> add if0
191> add if1
192> dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
201> bcn 100
15142> Wifi check: mode=AP+STA status=0
15143> Enabling/continuing uart log
30143> Wifi check: mode=AP+STA status=0
30143> Enabling/continuing uart log
45143> Wifi check: mode=AP+STA status=0
45143> Enabling/continuing uart log
So, one gigantic step forward and now one back.
Thanks for your previous and (hopefully) continuing help - much appreciated
Roy
…On Wed, Apr 6, 2022 at 9:48 AM Roy Kravitz ***@***.***> wrote:
Thanks. I put the esp_init_data_defaults at 0x80000. It didn't make any
difference - Same problem. Here's a snippet of the console log:
2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 4Mbit(256KB+256KB)
no GPIO select!
jump to run user1 @ 1000
rf_cal[0] !=0x05,is 0xFF
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8
I think I may know what's happening but I don't know what to do about it.
I tried running esptool to do the flashing instead of the ExpressIf utility
and got an error when trying to write user1.bin:
C:\Users\roykr\psuproj\esp-link\esptool>python esptool --port COM7 --baud
11520 write_flash --flash_freq 20m --flash_mode qio --flash_size 32m 0x1000
user1.bin 0x0000 boot_v1.6.bin 0x3fc000 esp_init_data_default.bin 0x3fe000
blank.bin
WARNING: Flash size arguments in megabits like '32m' are deprecated.
Please use the equivalent size '4MB'.
Megabit arguments may be removed in a future release.
esptool.py v3.2
Serial port COM7
Connecting....
Detecting chip type... Unsupported detection protocol, switching and
trying again...
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
WARNING: Detected crystal freq 20.89MHz is quite different to normalized
freq 26MHz. Unsupported crystal in use?
Crystal is 26MHz
MAC: 58:bf:25:d9:e6:e9
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00051fff...
Flash will be erased from 0x00000000 to 0x00000fff...
Flash will be erased from 0x003fc000 to 0x003fcfff...
Flash will be erased from 0x003fe000 to 0x003fefff...
Compressed 330756 bytes to 244619...
Writing at 0x00001000... (6 %)Traceback (most recent call last):
File "C:\Program
Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.3312.0_x64__qbz5n2kfra8p0\lib\runpy.py",
line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Program
Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.3312.0_x64__qbz5n2kfra8p0\lib\runpy.py",
line 87, in _run_code
exec(code, run_globals)
File "C:\Users\roykr\psuproj\esp-link\esptool\esptool\__main__.py", line
11, in <module>
esptool._main()
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 5136, in _main
main()
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 4602, in main
operation_func(esp, args)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 3873, in write_flash
esp.flash_defl_block(block, seq, timeout=timeout)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 154, in inner
return func(*args, **kwargs)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 918, in flash_defl_block
self.check_command("write compressed data to flash after seq %d" % seq,
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 495, in check_command
val, data = self.command(op, data, chk, timeout=timeout)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 458, in command
self.write(pkt)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\esptool.py",
line 421, in write
self._port.write(buf)
File
"C:\Users\roykr\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\serial\serialwin32.py",
line 325, in write
raise SerialTimeoutException('Write timeout')
serial.serialutil.SerialTimeoutException: Write timeout
Apparently esptool had trouble writing to that segment. I tried this on
several NodeMCU's and got the same failure. I tried writing all of the
other segments and that worked. The only write that failed was the one to
user1.bin. I tried writing user2.bin and had the same problem. The write
always hangs up 6% of the way in.
o Can you think of a reason why this would be happening? Have you seen
this before?
o Can I put user1.bin somewhere else in the flash?
Thanks
Roy
On Wed, Apr 6, 2022 at 8:43 AM Bartłomiej Zimoń ***@***.***>
wrote:
> blank.bin is to erase data and esp_init_data_defaults is to init this
> memory with defaults.
>
> —
> Reply to this email directly, view it on GitHub
> <#543 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAZF7J24ZHY4ROZ777FRJX3VDWWJZANCNFSM5PNXIBXA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
|
try this file, but decompress it with 7zip tool 3x, it is 3 times compressed zip,gzip,tar try first:
check if it work
|
I have success. I can connect to my home ssid. I have an ip address. I
think I'm good to go forward now.
Here's what it took:
o The python esptool failed the same way. With a timeout when trying to
write user1.bin. I tried both of your suggestions and then some. Nothing
worked. Couldn't get past the timeout at 6%
o I switched to NodeMCU flasher and flashed v3.2.47.alpha. w/ boot_v1.7 at
0x0000, user1.bin at 0x1000, esp_init_data_default.bin at 0x3fc000 and
blank.bin at 0x3fe000. I also flashed user1.bin to 0x81000 (which I'm
guessing is the backup partition).
o The ESP_Dxxx ssid showed up and I was able to connect. After switching
to STA+AP I was able to scan (something I couldn't do w/ the 3.0.14
version) and connect to my home network.
o I opened a browser page to the new IP address which brought up the
esp_link page and all looks good:
[image: image.png]
Just tried it on a 2nd NodeMCU, this time with user1.bin at 0x1000 and
user2.bin at 0x81000. Was able to join the ESP AP point, connect to my
home network, and get the esp-link web site at its assigned IP address.
Boot source was user1.bin - Yay! I think we're done. My conclusions:
o esptool is not as patient as the NodeMCU flasher. No timeouts, all
partitions got written to the device
o the later release did something to fix the problems I was having
o I couldn't have done this w/o your support. Thanks
Roy
…On Wed, Apr 6, 2022 at 11:32 AM Bartłomiej Zimoń ***@***.***> wrote:
try this file, but decompress it with 7zip tool 3x, it is 3 times
compressed zip,gzip,tar
esp-link-v3.2.47.alpha.24-g74e2043-dirty-Lucjan.tgz.zip
<https://github.com/jeelabs/esp-link/files/5889597/esp-link-v3.2.47.alpha.24-g74e2043-dirty-Lucjan.tgz.zip>
try first:
python esptool --port COM7 --baud 115200 write_flash --flash_freq 20m --flash_mode dio --flash_size 32m 0x1000
user1.bin 0x0000 boot_v1.7.bin 0x3fc000 esp_init_data_default.bin 0x3fe000 blank.bin
check if it work
2nd check this one:
python esptool --port COM7 --baud 115200 write_flash --flash_freq 20m --flash_mode dio --flash_size 32m 0x1000
user1.bin 0x0000 boot_v1.7.bin 0x3fc000 esp_init_data_default.bin 0x3fe000 blank.bin 0x80000 esp_init_data_default.bin
—
Reply to this email directly, view it on GitHub
<#543 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZF7J54HNQJIYRDSTEEZHTVDXKD3ANCNFSM5PNXIBXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
|
Hi everyone, here are the outputs for the 3.2 and 3.0 versions 2nd boot version : 1.7(5d6f877) rf_cal[0] !=0x05,is 0xFF ets Jan 8 2013,rst cause:2, boot mode:(3,7) load 0x40100000, len 2592, room 16 tail 0 chksum 0xf3 And 2nd boot version : 1.6 rf_cal[0] !=0x05,is 0xFF ets Jan 8 2013,rst cause:2, boot mode:(3,7) load 0x40100000, len 2408, room 16 tail 8 chksum 0xe5 Can anyone explain what is the issue and propose a way to fix for a newbee like me ? |
First try with DOUT flash mode |
Hi, Thanks Tried, does not work better. Flassing goes well with eithr DIO or DOUT (ESP flashing tool 3.9.2) but when booting it goes in the same loop. |
I really do not understand what is happening.
|
What is your flash size? |
If it is 32Mbit, you can try to use full flash attached in my previous posts |
No it is a plain 8Mbit . |
Tried to flash the 3.2.47 but stil the same issue |
Use esptool |
I wil try . Never used before. |
Unfortunately I have a strong disability ( I am a windows guy) |
Hi, I was able to use esptool for win |
I am coming back because nothing work. Can anyone offer a head to tail solution ? |
hi, Could you manage to fix this problem? |
Tried flashing in two steps. First blank.bin to 0x80000 and then
esp_init_data_default.bin go 0x80000.,
same result. Fast blinking green LED, no AP on either my phone or my
laptop.
Roy
…On Tue, Apr 5, 2022 at 4:08 PM Roy Kravitz ***@***.***> wrote:
I'll try it when I get home tonight but are those addresses correct? They
are both the same address so wouldn't esp_init_data_default overwrite
blank.bin?
Roy
On Tue, Apr 5, 2022 at 2:52 PM Bartłomiej Zimoń ***@***.***>
wrote:
> did you tries to flash blank.bin at 0x80000
> and next esp_init_data_default.bin 0x80000
>
> —
> Reply to this email directly, view it on GitHub
> <#543 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAZF7J7X3HTMX4XV6QDNLG3VDSYZ7ANCNFSM5PNXIBXA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
--
Roy Kravitz
Westside Program Director
Electrical and Computer Engineering Department
Maseeh College of Engineering and Computer Science
Portland State University
503-913-1678 (M)
***@***.***
ece.pdx.edu
|
@profroyk any debug log? try to find me on gitter.im |
I was able to flash using a modified CH340.
After reconnecting the device (with an unmodifed) USB Adapter, the blue led on the ESP8266 is flashing. No WiFi is available.
Does anybody have an idea what could be the reason for that.
thx for support.
The text was updated successfully, but these errors were encountered: