Skip to content
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

nRF51822 sometimes hard fault on connect #49313

Closed
korneliuszo opened this issue Aug 21, 2022 · 4 comments
Closed

nRF51822 sometimes hard fault on connect #49313

korneliuszo opened this issue Aug 21, 2022 · 4 comments
Assignees
Labels
area: Bluetooth Controller area: Bluetooth bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx priority: low Low impact/importance bug Stale
Milestone

Comments

@korneliuszo
Copy link

Describe the bug

I write code https://github.com/korneliuszo/lumiax-controller/
and it sometimes hardfaults on connection

To Reproduce
./scripts/tlay2_server.py - to connect to my UART protocol
./scripts/aaa.py - for trigger loop

Expected behavior
not crashing

Impact
It makes my device unusable

Logs and console output

It breaks on assert:

LL_ASSERT(!radio_is_ready());

Environment (please complete the following information):

  • OS: Linux
  • Toolchain Zephyr SDK=0.14.2
  • Commit 6fe1299
@korneliuszo korneliuszo added the bug The issue is a bug, or the PR is fixing a bug label Aug 21, 2022
@korneliuszo
Copy link
Author

korneliuszo commented Aug 22, 2022

Tried to run bt code only after bt_ready callback from bt_enable function.
Didn't help.

Stack:

Thread #8 536877040 (Name: main, prio:0,useropts:1) (Suspended : User Request)	
	arch_system_halt() at fatal.c:34 0x1a2d8	
	k_sys_fatal_error_handler() at fatal.c:46 0x1a2e0	
	z_fatal_error() at fatal.c:131 0x1a2fa	
	z_arm_fatal_error() at fatal.c:63 0x172ca	
	z_arm_fault() at fault.c:1,094 0x1f6c	
	z_arm_hard_fault() at fault_s.S:102 0x1fa6	
	<signal handler called>() at 0xfffffff1	
	isr_rx_pdu() at lll_scan.c:1,195 0x107f8	
	isr_rx() at lll_scan.c:766 0x107f8	
	isr_radio() at radio.c:140 0x11344	
	radio_nrf5_isr_body() at lll.c:93 0xf45a	
	radio_nrf5_isr() at lll.c:87 0xf45a	
	<signal handler called>() at 0xfffffffd	
	0xe500e7ea	
	0x80fffe	

@fabiobaltieri fabiobaltieri added the priority: low Low impact/importance bug label Aug 23, 2022
@carlescufi carlescufi added this to the future milestone Aug 24, 2022
@carlescufi carlescufi changed the title NRF51822 sometimes hard fault on connect nRF51822 sometimes hard fault on connect Aug 24, 2022
@carlescufi
Copy link
Member

@korneliuszo can you come up with a simple application that reproduces the problem? Your project is not trivial to set up.

@korneliuszo
Copy link
Author

hang.zip
Probably beacuse of this happens.
I use irqlock in fifo.hpp for atomically read 2 pointers.

@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth Controller area: Bluetooth bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx priority: low Low impact/importance bug Stale
Projects
None yet
Development

No branches or pull requests

6 participants