Cableguy, I understand what you say, but yet after the rubbish I get the LUA message. Anyway, I had a bit of success, and more baffling questions:
I tried to compile something on the arduino IDE, a ver basic program:
void setup() {
// put your setup code here, to run once:
pinMode(2, OUTPUT);
}
void loop() {
// put your main code here, to run repeatedly:
digitalWrite(2, HIGH); // turn the LED on (HIGH is the voltage level)
delay(100); // wait for a second
digitalWrite(2, LOW); // turn the LED off by making the voltage LOW
delay(100);
}
Which compiled OK, and provided that I plugged the ESP8266 board while pressing the FLASH button it includes to put it in flash mode, the Arduino ide flashed my code and the led started blinking as asked.
I repeat THE SAME power up and press flash button procedure for the B4R ide, using the same board parameters as arduino IDE, and B4R compiles and gives me the green on uploading it into the esp8266 board, but visually I can see there is no upload done, and the board starts blinking furiously, running my earlier, arduino IDE, compiled program, instead of the B4R code.
I am investigating it right now, any idea is welcome, and if I have success, of course I will document it here in case anyone else got stuck in this way.
At least now I do not get the LUA message (I suspect that by writing my blinking led code on the esp8266, I got rid of the LUA interpreter !!)
I SUSPECT the problem is at code uploading time: I can hear that B4R "resets" the COM port where the ESP8266 board is plugged in. That is: Windows makes the same sound as when I plug in the board.
This in turn seems to reset the ESP8266 board from flash mode, into run mode again. So the older code I compiled on the arduino IDE starts blinking the led, and the flash state is voided.
Regards, Enrique