Search found 4 matches
- Thu Jan 31, 2019 12:57 am
- Forum: ESP-IDF
- Topic: Using Interrupts on the UART
- Replies: 8
- Views: 20358
Re: Using Interrupts on the UART
Looking at your code a bit better, I think you're not using the driver correctly... you're supposed to either use uart_driver_install() so you can use all the nice queued read functions etc, or use uart_isr_register() to install your own ISR and handle all hardware things yourself. In your particul...
- Wed Jan 30, 2019 2:13 am
- Forum: ESP-IDF
- Topic: change the name of the device in STA mode
- Replies: 8
- Views: 16745
Re: change the name of the device in STA mode
Hey, it's not quite clear what your screenshot is showing and I don't know the exact issue. I guess it's showing physical devices currently connected to your AP? In that case, the shown device names probably rather identify your devices manufacturers (by MAC address OUI) than hostnames and you won't...
- Tue Jan 29, 2019 9:34 pm
- Forum: ESP-IDF
- Topic: Avoiding ESP_EARLY_LOG after code startup
- Replies: 2
- Views: 5873
Re: Avoiding ESP_EARLY_LOG after code startup
I'm happy to let you know I came up with a solution for our issue :) To avoid early logging and redirect it to UART1 (to some debug-uart pins) but also having the ability to printf to UART0 I did the following: In sdkconfig, I defined: CONFIG_CONSOLE_UART_CUSTOM=y CONFIG_CONSOLE_UART_NUM=1 CONFIG_CO...
- Tue Jan 29, 2019 6:39 am
- Forum: ESP-IDF
- Topic: Avoiding ESP_EARLY_LOG after code startup
- Replies: 2
- Views: 5873
Re: Avoiding ESP_EARLY_LOG after code startup
Its totally correct that ESP_EARLY_LOGx uses CONFIG_LOG_DEFAULT_LEVEL_DEBUG and not CONFIG_LOG_BOOTLOADER_LEVEL_NONE in that case, because "cpu_start" is handled after 2nd stage bootloader . Compare with the docs: https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/general-notes.html Fi...