How to compile AT Demo?
Posted: Mon Apr 18, 2016 6:35 pmHi, I know how to connect the 8266 hardware on Windows and I know how to dump and flash firmware and bootrom with esptool.py. I've installed an Ubuntu VM (no UI) in Hyper-V and compiled the toolchain (GitHub/pfalcon/esp-open-sdk). I'm a beginner with Ubuntu, so please forgive me for stupid questions.
I meanwhile forgot how I set up the VM and how to transfer the files to/from Windows, but I'm sure I'll find that out again. Probably somehow with mapping a network card and Putty or something.
Anyway, I would like to compile the standard firmware for the 8266 - the firmware that has the normal AT commands and all that. The firmware that is usually on the module when you freshly buy it. Is that the AT demo? If yes, how do I compile that? If I go to the folder ~/8266/esp-open-sdk/sdk/examples/at and run make, I just get "nothing to be done for 'FORCE'".
If I go to the folder ~/8266/esp-open-sdk/examples/blinky and run make, it compiles fine and creates me the two files blinky-0x00000.bin and blinky-0x40000.bin and also the blinky elf file, which I think I can use somehow to upload it.
I haven't tried to upload the compiled blinky yet (because of the format problems: no idea how to convert the elf file to the binary to upload), but anyway, I cannot compile AT demo and I need to know if this AT demo is the default firmware.
Can you help with that?
I can also restart with a fresh Ubuntu if necessary.
UPDATE: I found the link http://kacangbawang.com/latest-at-firmw ... 12k-flash/ which explains this problem and how to solve it. It seems like Expressif is just messed with file structure of their samples. I still couldn't fully compile yet (because of flash size restrictions), but I'm working on it.
I meanwhile forgot how I set up the VM and how to transfer the files to/from Windows, but I'm sure I'll find that out again. Probably somehow with mapping a network card and Putty or something.
Anyway, I would like to compile the standard firmware for the 8266 - the firmware that has the normal AT commands and all that. The firmware that is usually on the module when you freshly buy it. Is that the AT demo? If yes, how do I compile that? If I go to the folder ~/8266/esp-open-sdk/sdk/examples/at and run make, I just get "nothing to be done for 'FORCE'".
If I go to the folder ~/8266/esp-open-sdk/examples/blinky and run make, it compiles fine and creates me the two files blinky-0x00000.bin and blinky-0x40000.bin and also the blinky elf file, which I think I can use somehow to upload it.
I haven't tried to upload the compiled blinky yet (because of the format problems: no idea how to convert the elf file to the binary to upload), but anyway, I cannot compile AT demo and I need to know if this AT demo is the default firmware.
Can you help with that?
I can also restart with a fresh Ubuntu if necessary.
UPDATE: I found the link http://kacangbawang.com/latest-at-firmw ... 12k-flash/ which explains this problem and how to solve it. It seems like Expressif is just messed with file structure of their samples. I still couldn't fully compile yet (because of flash size restrictions), but I'm working on it.