summaryrefslogtreecommitdiff
path: root/src/esp32p4/uart.zig
diff options
context:
space:
mode:
Diffstat (limited to 'src/esp32p4/uart.zig')
-rw-r--r--src/esp32p4/uart.zig18
1 files changed, 1 insertions, 17 deletions
diff --git a/src/esp32p4/uart.zig b/src/esp32p4/uart.zig
index 15599423..a185737d 100644
--- a/src/esp32p4/uart.zig
+++ b/src/esp32p4/uart.zig
@@ -100,7 +100,7 @@ pub fn writeSome(bytes: []const u8) usize {
/// running on. Nothing is touched when it is not.
///
/// THE ONE EXCEPTION to this file's rule, and see the header for who may call it: not this file, not
-/// `app.zig`, only an image whose host side is opened at the same rate. `docs/registry.typ`
+/// `app.zig`, only an image whose host side is opened at the same rate. `docs/registry.pdf`
/// `BOARD-1` has the numbers — 921600 is one `UART_CLKDIV_SYNC` write on the existing 40 MHz XTAL,
/// int 43 frag 6, +0.064% error, and it takes a byte from 86.8 µs to 10.85 µs.
///
@@ -126,22 +126,6 @@ pub fn writeByte(b: u8) void {
uart0.pushByte(b);
}
-/// Emit `n` bytes read from `addr` as two hex digits each, computing the digits arithmetically so
-/// nothing here reads a lookup table. Used to answer "does a load from this address return what the
-/// linker put there", which is not a question a string literal can be trusted to ask.
-pub fn dumpHex(addr: u32, n: u32) void {
- const p: [*]const volatile u8 = @ptrFromInt(addr);
- var i: u32 = 0;
- while (i < n) : (i += 1) {
- const byte = p[i];
- for ([2]u8{ byte >> 4, byte & 0xf }) |nib| {
- writeByte(if (nib < 10) '0' + nib else 'a' + (nib - 10));
- }
- }
- writeByte('\r');
- writeByte('\n');
-}
-
/// A u32 as eight hex digits, reading no memory at all.
pub fn dumpWord(v: u32) void {
var shift: u5 = 28;