You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.[num-format](https://crates.io/crates/num-format): Crate for producing string representations of numbers, formatted according to international standards, e.g. "1,000,000" for US English - [](https://crates.io/crates/num-format)
1280
-
1.[`panic-persist`]: A panic handler crate inspired by `panic-ramdump` that logs panic messages to a region of RAM defined by the user, allowing for discovery of panic messages post-mortem using normal program control flow. - [](https://crates.io/crates/panic-persist)
1281
1281
1.[pc-keyboard]: A PS/2 keyboard protocol driver. Transport (bit-banging or SPI) agnostic, but can convert Set 2 Scancodes into Unicode. [](https://crates.io/crates/pc-keyboard)
1282
1282
1.[qei](https://crates.io/crates/qei) : A qei wrapper that allows you to extend your qei timers from a 16-bit integer to a 64-bit integer. - [](https://crates.io/crates/qei)
1283
1283
1.[qemu-exit]: Quit a running QEMU session with user-defined exit code. Useful for unit or integration tests using QEMU. - [](https://crates.io/crates/qemu-exit)
@@ -1299,8 +1299,8 @@ Work in progress drivers. Help the authors make these crates awesome!
1299
1299
1.[adafruit-bluefruit-protocol]: A `no_std` parser for the [Adafruit Bluefruit LE Connect controller protocol]. - [](https://crates.io/crates/adafruit-bluefruit-protocol)
1300
1300
1.[wtx](https://github.com/c410-f3r/wtx): Among other things, provides implementations to interact with HTTP, WebSockets and Databases.
@@ -1326,7 +1326,30 @@ Work in progress crates. Help the authors make these crates awesome!
1326
1326
-[OxCC](https://github.com/jonlamb-gh/oxcc): A port of Open Source Car Control written in Rust
1327
1327
-[Rubble](https://github.com/jonas-schievink/rubble): A pure-Rust embedded BLE stack [](https://crates.io/crates/rubble)
There are many ways to handle panics in embedded devices, these crates provide helpful variants.
1332
+
1333
+
1.[`dont_panic`] + [`dont_panic_slice`]: panic!()-like macro that causes linking error instead of panicking. May be used to statically ensure some code won't panic.
1334
+
1.[`no-panic`]: Attribute macro to require that the compiler prove a function can't ever panic.
1335
+
1.[`panic-abort`]: Causes an abort on panics (nightly-only)
1336
+
1.[`panic-halt`]: Halts the processor on panics
1337
+
1.[`panic-itm`]: Prints the panic through the chip's ITM to a debugger attached to the SWO pin (Cortex-M with ITM only)
1338
+
1.[`panic-never`]: This crate guarantees that your application is free of panicking branches.
1339
+
1.[`panic-persist`]: A panic handler crate inspired by `panic-ramdump` that logs panic messages to a region of RAM defined by the user, allowing for discovery of panic messages post-mortem using normal program control flow. - [](https://crates.io/crates/panic-persist)
1340
+
1.[`panic-ramdump`]: Writes the panic message into the beginning of RAM and enters an infinite loop; the message can be extracted by attaching a debugger (Cortex-M only)
1341
+
1.[`panic-semihosting`]: Prints the panic message via semihosting to an attached debugger (Cortex-M only)
0 commit comments