Discuss here different C compiler set ups, and compiling executables for the ESP8266

User avatar
By Necromant
#2429 Okay, folks. Endless reboot is fixed now. Looks like it's only happening on 'virgin' devices that never connected to a wireless network, when flashed. doing a wifi_set_opmode(0x0) will cause an exception as soon as the code enters main loop somewhere in the blobbies. This sets default mode upon startup to STA, and it should get fixed afterwards.
There's also a new command spi_wipe that wipes the whole flash clean. Could prove useful to get rid of any configuration leftovers that screw the blobs. As usual, grab the binaries at github and post about any bugs you've spotted.
Bonus in this update - SPI flash hexdump. For now addressesare in decimal only, sorry.

Code: Select allFrankenstein ESP8266 Firmware
Powered by Antares 0.2-rc1, Insane Mushroom
(c) Andrew 'Necromant' Andrianov 2014 <andrew@ncrmnt.org>
This is free software (where possible), published under the terms of GPLv2

Memory Layout:
data  : 0x3ffe8000 ~ 0x3ffe8aa8, len: 2728
rodata: 0x3ffe8ab0 ~ 0x3ffea254, len: 6052
bss   : 0x3ffea258 ~ 0x3fff1688, len: 29744
heap  : 0x3fff1688 ~ 0x3fffc000, len: 43384

 === Press enter to activate this console ===

blackblade > spi_dump 0 128
0000 - E9 03 00 00 04 00 10 40 00 00 10 40 DC 6C 00 00 ................
0010 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................
0010 - 04 0E 00 40 12 C1 F0 09 01 C5 13 00 01 FD FF C0 ................
0020 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................
0020 - 00 00 08 01 12 C1 10 0D F0 00 00 00 00 02 00 60 ................
0030 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................
0030 - 00 06 00 60 00 10 00 00 FF EF FF FF 00 80 28 00 ................
0040 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................
0040 - 41 FB FF 51 FB FF E6 22 24 21 FA FF C0 20 00 78 ................
0050 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................
0050 - 24 20 77 20 C0 20 00 79 24 62 A1 00 C0 20 00 32 ................
0060 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................
0060 - 25 80 60 33 20 C0 20 00 32 65 80 46 0E 00 B1 F2 ................
0070 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................
0070 - FF 0B 32 1B 62 20 62 B3 60 61 21 80 33 11 0B 66 ................
0080 - 00 00 00 00 E0 FE FF 3F E0 FE FF 3F DD 8F FE 3F ................

blackblade >
Last edited by Necromant on Mon Nov 10, 2014 3:11 pm, edited 1 time in total.
User avatar
By alonewolfx2
#2430 its working now but a little different. example i wrote "version" but console write ascii :)

Code: Select allspi_wipe   - Wipe the whole spi flash blank
             wipe

blackblade > .[Kv.[116D.[13C.[1C.[Ke.[116D.[13C.[2C.[Kr.[116D.[13C.[3C.[Ks.[116D.[13C.[4C.[Ki.[116D.[13C.[5C.[Ko.[116D.[13C.[6C.[Kn.[116D.[13C.[7C



Frankenstein ESP8266 Firmware
Powered by Antares 0.2-rc1, Insane Mushroom
(c) Andrew 'Necromant' Andrianov 2014 <andrew@ncrmnt.org>
This is free software (where possible), published under the terms of GPLv2




Necromant wrote:Okay, folks. Endless reboot is fixed now. Looks like it's only happening on 'virgin' devices that never connected to a wireless network, when flashed. doing a wifi_set_opmode(0x0) will cause an exception as soon as the code enters main loop somewhere in the blobbies. This sets default mode upon startup to STA, and it should get fixed afterwards.
There's also a new command spi_wipe that wipes the whole flash clean. Could prove useful to get rid of any configuration leftovers that screw the blobs. As usual, grab the binaries at github and post about any bugs you've spotted, will add hexdump shortly.
User avatar
By Necromant
#2432
alonewolfx2 wrote:its working now but a little different. example i wrote "version" but console write ascii :)


Likely a bug with your terminal software that's sending you unicode there. Try something VT100/VT102 compativle. minicom (I use this one), screen. putty if you're stuck on a windoze machine.
User avatar
By alonewolfx2
#2434 coolterm issue. you are right. putty working well.
but its not booting when i connect led to gpio 0 or gpio2 and power up module. why?


Necromant wrote:
alonewolfx2 wrote:its working now but a little different. example i wrote "version" but console write ascii :)


Likely a bug with your terminal software that's sending you unicode there. Try something VT100/VT102 compativle. minicom (I use this one), screen. putty if you're stuck on a windoze machine.