Sysprogs forums › Forums › VisualGDB › Bluetooth initialization fails ESP32
Tagged: esp32 bluetooth partition
- This topic has 2 replies, 2 voices, and was last updated 8 years, 7 months ago by
Frank.
-
AuthorPosts
-
March 8, 2017 at 14:42 #10599
Frank
ParticipantHi,
I’m having a problem with my Bluetooth initialization when I’m combining all the functionality I need. My program needs three things: Bluetooth, MQTT client over tls, HTTPS client.
When I build my program, any combination with two out of three work.
Building with all three components causes the ESP32 to crash during the Bluetooth initialization.
First some errors/warnings:
E (2596) phy_init: load_cal_data_from_nvs_handle: failed to get cal_data(4354)
W (2693) cpu_start: failed to load RF calibration data, falling back to full calibration
Then during the Bluetooth initialization:
BTDM CONTROLLER VERSION: 010101
btip start
copy .data from 4000d890 to 3ffae6e0, len 00001830
set .bss 0x0 from 3ffb8000 to 3ffbff70, len 00007f70
BTDM ROM VERSION 0101
BD_ADDR: 24:0A:C4:00:8D:8A
Guru Meditation Error of type IllegalInstruction occurred on core 0 at pc=40190840. Setting bp and returning..
Register dump:
PC : 0x40190840 PS : 0x00060130 A0 : 0x800823ba A1 : 0x3ffdeb10
A2 : 0x0000001b A3 : 0x0000001b A4 : 0x00000024 A5 : 0xffffffff
A6 : 0x00000000 A7 : 0xffffffff A8 : 0x8017d6a8 A9 : 0x3ffdeaf0
A10 : 0x00000000 A11 : 0x3ffdeaa2 A12 : 0x3ffdea4f A13 : 0x00000041
A14 : 0x00000000 A15 : 0x3ffdea53 SAR : 0x00000005 EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x4000c46c LEND : 0x4000c477 LCOUNT : 0x00000000Backtrace: 0x40190840:0x3ffdeb10 0x400823ba:0x3ffdeb30 0x400823fd:0x3ffdeb60 0x4008249d:0x3ffdeb80 0x40118977:0x3ffdeba0
I have put the build logs, output logs and some additional information on pastebin. I suspect it is a nvs(flash) issue since the image corrupts after. Might it be overwriting the Bluetooth flash data?
Any ideas on how to fix this?
Topic on ESP32 Forum
March 9, 2017 at 05:08 #10604support
KeymasterHi,
Sorry, we are not the vendor for the ESP32 IDF and hence can only provide help on issues related to VisualGDB. If you can confirm that this problem only happens when using VisualGDB and not when building from the ESP-IDF directly, we will re-investigate it, but otherwise the ESP32 forum is the best place to seek advice on this.
March 9, 2017 at 14:02 #10608Frank
ParticipantMy program exceeded 1M specified in the default partition table, writing a partition csv and generating a binary from that and editing esp32.xml to specify the correct partition table file solved my problems.
http://esp-idf.readthedocs.io/en/latest/partition-tables.html
Thanks anyway.
-
AuthorPosts
- You must be logged in to reply to this topic.