ESP8266 Community Forum

- Sun Sep 07, 2014 9:28 am #297 thank you.

now the IoT demo runs on the module without errors.

- Sun Sep 07, 2014 10:30 am #299

thank you.

now the IoT demo runs on the module without errors.

Yeah, great

And I still haven't receive mine yet...

Now, we need to get rid of the original SDK and replace it with a FOSS toolchain:

• working GNU toolchain (some Xtensa support person seems to be helping us on that)
• convert the "gen_misc.bat" DOS script into Bash or Python: should be easy
• replace the "genflashbin.exe" tool by a portable tool: almost done using Kongo's parsebin.py
• replace the "XTCOM_UTILITY" by a free (and more convenient) download tool: done using Kongo's esptool
• replace the static libraries in lib by open-source equivalent: BIG task, unless some of them are based on FOSS already, but can use objdup disassembly if required
• RE and document the existing functions in ROM: BIG task too!
• find out if there is a way to change the ROM contents: if yes, do it!

EDIT: however, for the last point, I fear that it is OTP and cannot be changed further. Not a big problem though, but could be nice to get rid of the Flash chip and have a small app running within the SoC itself

- Sun Sep 07, 2014 3:16 pm #327

thank you.

now the IoT demo runs on the module without errors.

Wow, great! Did you do anything special to make it work?

In other news, the ROM dump I made (esp8266.bin, md5 55eb884ecb257da22d9992a802134ff7) is actually corrupt, due to a protocol bug in esptool, which I have since fixed. I am very sorry for having wasted everybody's time. I just got a little bit excited and wanted to share the stuff

The new dump (http://df.lth.se/~kongo/esp8266.bin/iram0.bin, 7b52074c61442ee4c45f59d026313fa3), should hopefully be correct.
I have made an symbol-annotated disassembly for reference (http://df.lth.se/~kongo/esp8266.bin/iram0.txt), and it looks much more sane.

I'm planning to clean up esptool, probably integrating the image creation stuff, or perhaps make it read ELF and split it up automagically. Any and all feedback is welcome.

- Sun Sep 07, 2014 3:51 pm #331

In other news, the ROM dump I made (esp8266.bin, md5 55eb884ecb257da22d9992a802134ff7) is actually corrupt, due to a protocol bug in esptool, which I have since fixed. I am very sorry for having wasted everybody's time. I just got a little bit excited and wanted to share the stuff

The new dump (http://df.lth.se/~kongo/esp8266.bin/iram0.bin, 7b52074c61442ee4c45f59d026313fa3), should hopefully be correct.
I have made an symbol-annotated disassembly for reference (http://df.lth.se/~kongo/esp8266.bin/iram0.txt), and it looks much more sane.

I'm planning to clean up esptool, probably integrating the image creation stuff, or perhaps make it read ELF and split it up automagically. Any and all feedback is welcome.

Don't be sorry, you did a wonderful job anyway!

I am not a Python fan, but I agree this is the most universal portable script language available, so I think it is the best choice for this kind of tools, plus it can easily be extended with a graphical front-end. don't misunderstand me, I am a big fan of the command line, but it makes things easier for newcomers to have buttons and dialog windows, I agree.

So first do a command-line tool, then a GUI for it.

A tool that could split the a.out file to generate all the dump, disassembly, flash.bin and irom0text.bin files in one single step, then flash these last 2 files would be far much better than the original mix of DOS batch, Python script and C executable files!