Skip to content
This repository has been archived by the owner on May 6, 2021. It is now read-only.

nimBLE test application to reproduce assertion fails with extended advertisings

License

Notifications You must be signed in to change notification settings

janosbrodbeck/nimble_app_assertion_fail

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

NimBLE extended advertising - assertion fail test app

Building / flashing

Targets for nrf52dk and nrf52840dk are already provided.
(For nrf52840dk replace nrf52 with nrf52840 in target names)

  • Prepare repo newt upgrade
  • Build bootloader: newt build nrf52_boot
  • Build app: newt build nrf52_ext_app
  • Create image: newt create-image nrf52_ext_app 1.0.0
  • Load bootloader: newt load nrf52_boot
  • Load app newt load nrf52_ext_app

Open terminal (e.g. pyterm -p /dev/tty...).

Use the app

Flash the application on two nodes. One will serve as consumer the other as producer.

Producer: Start with producer <interval>, interval given in ms. Recommended values: 200 to 500 as starting points. This should trigger the issue very fast.
Consumer: Start with entering consumer into the console

The lower, the faster the crash can be triggered. Would not recommend to go below 200/250ms.

About the producer/consumer:

Producer produces marked packets every <interval> ms and scans for packets (processes them but does not advertise them back again).
Consumer just scans for marked packets and advertises them back without any changes.

About

nimBLE test application to reproduce assertion fails with extended advertisings

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages