cesanta/mongoose

Embedded web server for C/C++

Nijeesh Joshy

@nijeesh4all

hi guys

Max VonSydow

@maxvonsydow_gitlab

/pass

Suryaobulareddy

@Suryaobulareddy

Hi Guys,
any one tried mqtt in c
I tried https://github.com/cesanta/mongoose-os/tree/master/fw/examples/c_mqtt this example but unable initiate the connection

zkauker

@zkauker

Hi guys. Can anyone help me in obtaining the local random UDP port when i'm creating a new UDP connection using mg_connect()?
Is that available somewhere in the struct mg_connection parameter in the event callback method?

abhishek125

@abhishek125

As far as i know every esp has unique MAC address which also serves as its client id, but I am facing duplicate client id issue with aws provisioned esp devices. I confirmed the same with aws support and cloudwatch logs.could anyone please give me any clue how this kind of issue is possible.

i am using nodemcu esp8266 with mongoose os

Manfred Müller-Späth

@mamuesp

@abhishek125 - Unfortunately you are in the wrong conversation, this is for mongoose, Cesantas web server, not mongoose-os, but there your question should be posted.

SURYA OBULA REDDY NARAPUREDDY

@suryaobulareddy_gitlab

@suryaobulareddy_gitlab
Hi Guys,
Currently I'm working on esp32 using mongoose
I tried to compile free rtos with mongoose
but I'm able to compile but module were continuously getting restart
for ref:

void mg_task(void *arg) {
  printf("mg_task started\r\n");
  while (1) {
    mgos_msleep(100);
  }
  vTaskDelete(NULL);
}
enum mgos_app_init_result mgos_app_init(void){//void user_init(void) {

  printf("Free RAM: \r\n");//, system_get_free_heap_size());
  xTaskCreate(mg_task,"mongoose",1024, NULL, 0, NULL);
  printf("%s", "hello, my task");
              //MG_TASK_STACK_SIZE / 4, /* in 32-bit words */
              //NULL, MGOS_TASK_PRIORITY, NULL);
 //xTaskCreatePinnedToCore(&my_task, "tskmad", 2048, NULL, 5, NULL, 0);
 // while (1);
  return MGOS_APP_INIT_SUCCESS;
}

rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)<CR><LF>
configsip: 0, SPIWP:0xee<CR><LF>
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00<CR><LF>
mode:DIO, clock div:1<CR><LF>
load:0x3fff0018,len:4<CR><LF>
load:0x3fff001c,len:6188<CR><LF>
load:0x40078000,len:9592<CR><LF>
load:0x40080400,len:6944<CR><LF>
entry 0x40080740<CR><LF>
<ESC>[0;33mW (58) boot: PRO CPU has been reset by WDT.<ESC>[0m<CR><LF>
<ESC>[0;33mW (58) boot: WDT reset info: PRO CPU PC=0x400803c0<ESC>[0m<CR><LF>
<ESC>[0;33mW (58) boot: WDT reset info: APP CPU PC=0x8a9e2587<ESC>[0m<CR><LF>
<ESC>[0;32mI (64) boot: ESP-IDF v3.2-r2 2nd stage bootloader<ESC>[0m<CR><LF>
<ESC>[0;32mI (69) boot: compile time 12:43:38<ESC>[0m<CR><LF>
<ESC>[0;32mI (73) boot: Enabling RNG early entropy source...<ESC>[0m<CR><LF>
<ESC>[0;32mI (79) qio_mode: Enabling default flash chip QIO<ESC>[0m<CR><LF>
<ESC>[0;32mI (84) boot: SPI Speed : 80MHz<ESC>[0m<CR><LF>
<ESC>[0;32mI (88) boot: SPI Mode : QIO<ESC>[0m<CR><LF>
<ESC>[0;32mI (92) boot: SPI Flash Size : 4MB<ESC>[0m<CR><LF>
<ESC>[0;32mI (96) boot: Partition Table:<ESC>[0m<CR><LF>
<ESC>[0;32mI (100) boot: ## Label Usage Type ST Offset Length Flags<ESC>[0m<CR><LF>
<ESC>[0;32mI (108) boot: 0 nvs WiFi data 01 02 00009000 00004000 00000000<ESC>[0m<CR><LF>
<ESC>[0;32mI (116) boot: 1 otadata OTA data 01 00 0000d000 00002000 00000000<ESC>[0m<CR><LF>
<ESC>[0;32mI (125) boot: 2 app_0 OTA app 00 10 00010000 00180000 00000000<ESC>[0m<CR><LF>
<ESC>[0;32mI (133) boot: 3 fs_0 SPIFFS 01 82 00190000 00040000 00000000<ESC>[0m<CR><LF>
<ESC>[0;32mI (141) boot: 4 app_1 OTA app 00 11 001d0000 00180000 00000000<ESC>[0m<CR><LF>
<ESC>[0;32mI (150) boot: 5 fs_1 SPIFFS 01 82 00350000 00040000 00000000<ESC>[0m<CR><LF>
<ESC>[0;32mI (158) boot: End of partition table<ESC>[0m<CR><LF>
<ESC>[0;32mI (162) boot: OTA data 0: seq 0x00000001, st 0x10, CRC 0x157a2b85, valid? 1<ESC>[0m<CR><LF>
<ESC>[0;32mI (170) boot: OTA data 1: seq 0x00000000, st 0x00, CRC 0x00000000, valid? 0<ESC>[0m<CR><LF>
<ESC>[0;32mI (177) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x245d0 (148944) map<ESC>[0m<CR><LF>
<ESC>[0;32mI (225) esp_image: segment 1: paddr=0x000345f8 vaddr=0x3ffb0000 size=0x0253c ( 9532) load<ESC>[0m<CR><LF>
<ESC>[0;32mI (228) esp_image: segment 2: paddr=0x00036b3c vaddr=0x40080000 size=0x00400 ( 1024) load<ESC>[0m<CR><LF>
<ESC>[0;32mI (232) esp_image: segment 3: paddr=0x00036f44 vaddr=0x40080400 size=0x090cc ( 37068) load<ESC>[0m<CR><LF>
<ESC>[0;32mI (252) esp_image: segment 4: paddr=0x00040018 vaddr=0x400d0018 size=0xa9c60 (695392) map<ESC>[0m<CR><LF>
<ESC>[0;32mI (434) esp_image: segment 5: paddr=0x000e9c80 vaddr=0x400894cc size=0x07b30 ( 31536) load<ESC>[0m<CR><LF>
<ESC>[0;32mI (453) boot: Loaded app from partition at offset 0x10000<ESC>[0m<CR><LF>
<ESC>[0;32mI (454) boot: Disabling RNG early entropy source...<ESC>[0m<CR><LF>
<ESC>[0;32mI (454) cpu_start: Pro cpu up.<ESC>[0m<CR><LF>
<ESC>[0;32mI (458) cpu_start: Single core mode<ESC>[0m<CR><LF>
<ESC>[0;32mI (462) heap_init: Initializing. RAM available for dynamic allocation:<ESC>[0m<CR><LF>
<ESC>[0;32mI (469) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM<ESC>[0m<CR><LF>
<ESC>[0;32mI (475) heap_init: At 3FFBA588 len 00025A78 (150 KiB): DRAM<ESC>[0m<CR><LF>
<ESC>[0;32mI (481) heap_init: At 3FFE0440 len 0001FBC0 (126 KiB): D/IRAM<ESC>[0m<CR><LF>
<ESC>[0;32mI (488) heap_init: At 40078000 len 00008000 (32 KiB): IRAM<ESC>[0m<CR><LF>
<ESC>[0;32mI (494) heap_init: At 40090FFC len 0000F004 (60 KiB): IRAM<ESC>[0m<CR><LF>
<ESC>[0;32mI (500) cpu_start: Pro cpu start user code<ESC>[0m<CR><LF>
<ESC>[0;32mI (181) cpu_start: Starting scheduler on PRO CPU.<ESC>[0m<CR><LF>
mgos_hal_freertos.c:177 rtos 1.0 (20190326-164015)<CR><LF>
mgos_hal_freertos.c:179 Mongoose OS 2.12.1 (20190326-124823/2.12.1-gdd403d6)<CR><LF>
mgos_hal_freertos.c:182 CPU: 160 MH

run time execption
If any one knows please help me

Ryan Truer

@rtrue983

@suryaobulareddy_gitlab i think you are in the wrong chat... use mongoose-os

avpaneendra

@avpaneendra

please help for flashing esp01 in MangooseOS

Pim van Pelt

@pimvanpelt

Esp01 doesn’t have enough flash for Mongoose OS

Also, this is the wrong channel for Mongoose OS

majorninth

@majorninth

I have a problem connecting to aws with a esp32 dev kit. I have existing certificates, key and policy for an existing aws connection that I use for testing various wifi boards. I setup my esp32 kit to point to my aws site and filled in all the proper information in the config files. AWS gives me a -2700 error (bad certificate). I have no problems connecting with non mongoose boards and I have no problem connecting to my own MQTT server (with different certs and key). Is there anything special about mongoose that wants its own type of cert/key rather than something that was generated directly in the aws cli rather than using the mongoose aws setup iot default command?

Liviu

@nliviu

This is the wrong channel for Mongoose OS. https://gitter.im/cesanta/mongoose-os

Karthik Desai

@karthikdesai

@cpq Sorry for the late reply. (Regarding the memory leaks question). Here is the valgrind-log gist again https://gist.github.com/karthikdesai/6380c611062e38c1a7944d15ef3c12eb
The server was run for around a min. And from the log we see that:

mg_mgr_init_opt (mongoose.c:2609) (on the log https://gist.github.com/karthikdesai/6380c611062e38c1a7944d15ef3c12eb#file-valgrind_output-log-L299)
mg_if_create_iface (mongoose.c:3648) (on the log https://gist.github.com/karthikdesai/6380c611062e38c1a7944d15ef3c12eb#file-valgrind_output-log-L601)
mg_http_create_proto_data (mongoose.c:6030) (on the log https://gist.github.com/karthikdesai/6380c611062e38c1a7944d15ef3c12eb#file-valgrind_output-log-L1859)
mg_create_connection_base (mongoose.c:2739) (on the log https://gist.github.com/karthikdesai/6380c611062e38c1a7944d15ef3c12eb#file-valgrind_output-log-L2508)
functions had 'still reachable' loss record on valgrind. Can this be some how fixed or is there some steps that i have missed? Thanks!

Sergey Lyubka

@cpq

@karthikdesai yes, please make sure there are no leaks from your own application first. When you can show valgrind output with only mongoose records, we might take a look.

Karthik Desai

@karthikdesai

@cpq Unfortunately these leaks are from other libraries i have no control over :(

Sergey Lyubka

@cpq

@karthikdesai i am not sure that mongoose is to blame here - it could be that your application is guilty, not mongoose

if you're convinced that mongoose is guilty, then provide a failing test in test/unit_test.c , we'll take a look

engrziarehman

@engrziarehman

i have a problem in rpc command,
mos --port mqtt://my.mqtt.server:1883/esp32_6732ac ls
above command run successfully when there is no authentication required, but when username and password was configured in mqtt broker, then what will be the method in rpc command to add username and password to execute rpc commands through mqtt. kindly help.

Liviu

@nliviu

@engrziarehman Wrong channel. Try https://gitter.im/cesanta/mongoose-os

YueBing Tao

@kof98765

@kof98765
while (1)
{
//reconnect process
if (mqttConnectState < 0)
{
mg_mgr_free(&mgr);
mg_mgr_init(&mgr, NULL);

        snprintf(port, sizeof(port), "%s:%d", GetSettings2("reportIp","127.0.0.1"),1883);

        nc = mg_connect(&mgr, port, report_handler);
        if (nc)
        {
            mg_set_timer(nc, mg_time() + 2.5);
            mqttConnectState = 0;
        }
    }
    mg_mgr_poll(&mgr, 10);
}

/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7ffff735a7e5]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7ffff7367698]
/root/x64/env/dataMonitor[0x43d820]
/root/x64/env/dataMonitor(mg_destroy_conn+0x6c)[0x42ca65]
/root/x64/env/dataMonitor[0x42cb56]
/root/x64/env/dataMonitor(mg_socket_if_poll+0x795)[0x43072b]
/root/x64/env/dataMonitor(mg_mgr_poll+0x9b)[0x42cf92]

this is a mqtt client code

Mark

@markterrill

Pim ...

Pim van Pelt

@pimvanpelt

hey :)

Mark

@markterrill

howdy.

so is the HA library a mqtt client ?

Pim van Pelt

@pimvanpelt

just FYI, this is the underlying library Mongoose

the thing you're looking for is Mongoose OS

Mark

@markterrill

yeah

Pim van Pelt

@pimvanpelt

but yes, I started a library a few weeks ago

Mark

@markterrill

have any public code ?

Pim van Pelt

@pimvanpelt

because my wall switches and relays and thermo/hydro/baro etc sensors want to be exposed in my HA

Mark

@markterrill

oki

Pim van Pelt

@pimvanpelt

and I didn't like the alternatives like esphome and tasmota

I haven't really finished the library yet but I am willing to put it online for you to play with

some caveats: before I submit it to mongoos-os-libs/ it needs a few strong use cases

currently all it does is expose gpio and a few sensors

and it's not complete (and as well I have not run it in production, only in a few test instances where it seems to work well with MQTT auto discovery)

YueBing Tao

@kof98765

@pimvanpelt ...

YueBing Tao

@kof98765

@pimvanpelt

void mbuf_resize(struct mbuf a, size_t new_size) {
if(new_size==0)//if new_size ==0 will free(a->buf)?????
return;
if (new_size > a->size || (new_size < a->size && new_size >= a->len)) {
char buf = (char *) MBUF_REALLOC(a->buf, new_size);

Francesco

@fcolasante_gitlab

Anyone use GCP on ESP32?

I have some problem... My device continously disconnett to MQTT broker

[Jun 24 21:21:10.776] SW ECDSA verify curve 3 hash_len 32 sig_len 71
[Jun 24 21:21:11.200] SW ECDH curve 3
[Jun 24 21:21:11.726] mgos_mqtt_conn.c:227    MQTT0 TCP connect ok (0)
[Jun 24 21:21:12.085] mgos_mqtt_conn.c:271    MQTT0 CONNACK 0
[Jun 24 21:21:12.085] mgos_mqtt_conn.c:208    MQTT0 sub /devices/esp32_7C21F0/commands/# @ 1
[Jun 24 21:21:12.091] mgos_mqtt_conn.c:208    MQTT0 sub /devices/esp32_7C21F0/config @ 1
[Jun 24 21:21:12.189] mgos_mqtt_conn.c:253    MQTT0 Disconnect
[Jun 24 21:21:12.189] mgos_mqtt_conn.c:544    MQTT0 connecting after 1883 ms
[Jun 24 21:21:14.080] mgos_mqtt_conn.c:468    MQTT0 connecting to mqtt.2030.ltsapis.goog:8883
[Jun 24 21:21:14.278] mg_ssl_if_mbedtls.c:31  0x3ffc8ee8 ciphersuite: TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
[Jun 24 21:21:14.297] SW ECDSA verify curve 3 hash_len 32 sig_len 72
[Jun 24 21:21:14.727] SW ECDSA verify curve 3 hash_len 32 sig_len 72
[Jun 24 21:21:15.154] SW ECDSA verify curve 3 hash_len 32 sig_len 71

Liviu

@nliviu

Try the mongoose-os channel https://gitter.im/cesanta/mongoose-os

Mark

@markterrill

@fcolasante_gitlab turn up debugging and look to see if it's saying certificate error and then rebooting the device. If so, do the gcp provision script again.

Where communities thrive

People

Repo info

Activity