Skip to content

CONFIG_BT leads Fatal fault in ISR on esp32 #13065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lilrom13 opened this issue Feb 5, 2019 · 5 comments
Closed

CONFIG_BT leads Fatal fault in ISR on esp32 #13065

lilrom13 opened this issue Feb 5, 2019 · 5 comments
Assignees
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug platform: ESP32 Espressif ESP32

Comments

@lilrom13
Copy link

lilrom13 commented Feb 5, 2019

Describe the bug
Add CONFIG_BT=y leads a Fatal fault in ISR! Spinning... on esp32.

To Reproduce
add CONFIG_BT=y to prj.conf
also reproducible with beacon sample

  1. cd build/
  2. cmake -GNinja -DBOARD=esp32 ..
  3. ninja
  4. cd ..
  5. west -v flash -d build/ --skip-rebuild --esp-device /dev/tty.SLAB_USBtoUART

** FATAL EXCEPTION ** CPU 0 EXCCAUSE 3 PS 0x00060020 PC 0x40082a23 VADDR 0x400805f8 ** A0 0x80082a4e SP 0x3ffb2cd0 A2 0x400805ec A3 0x00000000 ** A4 0x00000001 A5 0x3ffb4570 A6 0x3ffb2034 A7 0x00060d23 ** A8 0x80082a0d A9 0x3ffb2ca0 A10 0x00000000 A11 0x00000000 ** A12 0x00000000 A13 0x3ffb4550 A14 0x00000000 A15 0x00000000 ** LBEG 0x00000000 LEND 0x00000000 LCOUNT 0x00000000 ** SAR 0x00000000 Current thread ID = 0x3ffb2034 Faulting instruction address = 0xdeaddead Fatal fault in ISR! Spinning...

Environment (please complete the following information):

  • OS: MacOS
  • Toolchain: ESP-IF
@lilrom13 lilrom13 added the bug The issue is a bug, or the PR is fixing a bug label Feb 5, 2019
@jhedberg
Copy link
Member

jhedberg commented Feb 8, 2019

@galak I'm not at all familiar with esp32, and don't have any such HW. In fact, I didn't even realize we supported Bluetooth on it, so I'm not sure what I can do about this issue.

@lilrom13 how is Bluetooth supposed to work on your board? E.g. which HCI driver are you using?

@nashif
Copy link
Member

nashif commented Feb 10, 2019

bluetooth not supported on this platform.

@nashif nashif closed this as completed Feb 10, 2019
@WilliamGFish
Copy link
Collaborator

@nashif
Interesting article was published on how the Expressif team have released their version of BLE Mesh which has been built on top of Zephyr (as below).

It might be worth a conversation to see if they are willing to contribute to the overall Zephyr code base.

https://www.espressif.com/en/news/Espressifs_BLE_Mesh_SDK_Is_Now_Bluetooth_SIG_certified

@jhedberg
Copy link
Member

jhedberg commented Mar 4, 2019

@WilliamGFish thanks for pointing out the Espressif Mesh SDK. I'm happy proper credit is given to the Zephyr stack, since it's something that doesn't always happen in situations like this. From a quick look the main thing that might be worth looking at for Zephyr is the provisioner support since it's something we don't have. It looks like there might be some standard models code we could benefit from as well. Besides that, I wouldn't expect there to be much to port qualification-wise, since we do run all the relevant tests periodically, despite not having a formal qualification listing for the mesh stack.

@EddLeon
Copy link

EddLeon commented Jun 14, 2019

@nashif Is there any future plan to support Bluetooth?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug platform: ESP32 Espressif ESP32
Projects
None yet
Development

No branches or pull requests

6 participants