You can chat about native SDK questions and issues here.

User avatar
By de1m
#68033 Hi,
I've installed the esp-open-sdk on my linux.
The previously version that I've used was the SDK V1.5 and with this version working my esp12 without any problem.
Now for a new project I've installed the V2.0.0_16_08_10 and compiled for a test the same blinky example (this has worked on sdk 1.5). But now my esp12 don't working(after compiling and flash). I saw that the adddress was changed from 0x4000 to 0x1000, is this a problem?

Code: Select all#include "ets_sys.h"
#include "osapi.h"
#include "gpio.h"
#include "os_type.h"
#include "driver/uart.h"

// ESP-12 modules have LED on GPIO2. Change to another GPIO
// for other boards.
static const int pin = 2;
static volatile os_timer_t some_timer;

void some_timerfunc(void *arg)
{
  //Do blinky stuff
  if (GPIO_REG_READ(GPIO_OUT_ADDRESS) & (1 << pin))
  {
    // set gpio low
    gpio_output_set(0, (1 << pin), 0, 0);
  }
  else
  {
    // set gpio high
    gpio_output_set((1 << pin), 0, 0, 0);
  }
  os_printf("STA Mode - Client reconnected\r\n");
}

void ICACHE_FLASH_ATTR user_init()
{
  // init gpio subsytem
  gpio_init();

  // configure UART TXD to be GPIO1, set as output
  PIN_FUNC_SELECT(PERIPHS_IO_MUX_U0TXD_U, FUNC_GPIO1);
  gpio_output_set(0, 0, (1 << pin), 0);

  uart_init(BIT_RATE_9600,BIT_RATE_9600);

  // setup timer (500ms, repeating)
  os_timer_setfn(&some_timer, (os_timer_func_t *)some_timerfunc, NULL);
  os_timer_arm(&some_timer, 500, 1);
}
User avatar
By cpeacock
#68370 I'm having the same trouble with esp-open-sdk/SDK V2.0.0_16_08_10 on ubuntu 17.04. Blinky builds o.k., but when I flash it to my NodeMCU (ESP-12-E Core), I get nothing.

If I use Arduino to test the I/O pin, it works fine.

I can't help you with the new flash location (0x10000 vs 0x40000). I'm new to the environment and had a poke around in the linker script files (eagle.app.v6.ld), but don't really have a feel for what is wrong, nor where the 0x10000 is defined. It refers to the SPI flash memory location which appears to be correct.
User avatar
By cpeacock
#68435 I'm having the same trouble, sadly. I've compiled with SDK_V2.0.0_16_08_10, SDK_V1.5.4_16_05_20 and SDK-2.1.0.

I don't think the SDK is at fault - it looks more like the build tools.

Once I've flashed blinky and reset the bootloader shows:

Code: Select all ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 32052, room 16
tail 4
chksum 0xef
load 0x33333333, len 858993459, room 4



I'm no expert, but I expect to see a csum followed by ~ld. With the excessive length of 858993459 bytes, I suspect the second lot of code never completes loading from SPI Flash. Could this suggest something wrong with elf2image or the script generating the blinky-0x10000.bin file?