Overhall w/ slides

WEEK01/WEEK01-04.md

@@ -1,4 +1,4 @@
-# Embedded Systems Reverse Engineering
+# Embedded Systems Reverse Engineering
 [Repository](https://github.com/mytechnotalent/Embedded-Hacking)
 
 ## Week 1
@@ -33,7 +33,7 @@ Before you start, make sure:
 - You have **GDB** (specifically `arm-none-eabi-gdb`) installed
 - Your binary file (`0x0001_hello-world.elf`) is available in the `build/` directory
 
-## Step-by-Step Instructions
+#### Step-by-Step Instructions
 
 ##### Step 1: Start OpenOCD in Terminal 1
 
@@ -64,12 +64,12 @@ Info : accepting 'gdb' connection on tcp/3333
 Open a **second terminal window** and navigate to your project directory:
 
 ```
-arm-none-eabi-gdb -q build/0x0001_hello-world.elf
+arm-none-eabi-gdb build\0x0001_hello-world.elf
 ```
 
 **Expected Output:**
 ```
-Reading symbols from build/0x0001_hello-world.elf...
+Reading symbols from build\0x0001_hello-world.elf...
 (gdb)
 ```
 
@@ -257,37 +257,37 @@ Based on what you've observed:
 - Are they the same?
 - __________
 
-## Deeper Exploration (Optional Challenge)
+#### Deeper Exploration (Optional Challenge)
 
-### Challenge 1: Step Through stdio_init_all
+##### Challenge 1: Step Through stdio_init_all
 1. Continue stepping: `si` (step into) or `ni` (next instruction)
 2. Eventually, you'll reach `bl 0x1000156c <stdio_init_all>`
 3. Use `si` to step **into** that function
 4. What instructions do you see?
 5. What registers are being modified?
 
-### Challenge 2: View Specific Registers
+##### Challenge 2: View Specific Registers
 Instead of viewing all registers, you can view just a few:
 ```gdb
 i r pc sp lr r0 r1 r2
 ```
 This shows only the registers you care about.
 
-### Challenge 3: Examine Memory
+##### Challenge 3: Examine Memory
 To examine memory at a specific address (e.g., where the string is):
 ```gdb
 x/16b 0x100019cc
 ```
 This displays 16 bytes (`b` = byte) starting at address `0x100019cc`. Can you see the "hello, world" string?
 
-### Challenge 4: Set a Conditional Breakpoint
+##### Challenge 4: Set a Conditional Breakpoint
 Set a breakpoint that only triggers after a certain condition:
 ```gdb
 b *0x1000023a if $r0 != 0
 ```
 This is useful when you want to break on a condition rather than every time.
 
-## Questions for Reflection
+#### Questions for Reflection
 
 1. **Why does GDB show both the C source line AND the assembly?**
    - This is because the .elf file contains debug symbols
@@ -304,7 +304,7 @@ This is useful when you want to break on a condition rather than every time.
    - `si` steps into function calls
    - `ni` executes entire functions without stopping inside them
 
-## Important GDB Commands Reference
+#### Important GDB Commands Reference
 
 | Command                | Short Form | What It Does                         |
 | ---------------------- | ---------- | ------------------------------------ |
@@ -324,30 +324,30 @@ This is useful when you want to break on a condition rather than every time.
 - `x/16b 0x20000000` - examine 16 bytes starting at RAM address
 - `x/4w 0x10000000` - examine 4 words (4-byte values) starting at Flash address
 
-## Troubleshooting
+#### Troubleshooting
 
-### Problem: "OpenOCD not found"
+##### Problem: "OpenOCD not found"
 **Solution:** Make sure OpenOCD is in your PATH or use the full path to the executable
 
-### Problem: "Target not responding"
+##### Problem: "Target not responding"
 **Solution:** 
 - Check that your Pico 2 is properly connected
 - Make sure OpenOCD is running and shows "accepting 'gdb' connection"
 - Restart both OpenOCD and GDB
 
-### Problem: "Cannot find breakpoint at main"
+##### Problem: "Cannot find breakpoint at main"
 **Solution:** 
 - Make sure you compiled with debug symbols
 - The .elf file must include symbol information
 - Try breaking at an address instead: `b *0x10000234`
 
-### Problem: GDB shows "No source available"
+##### Problem: GDB shows "No source available"
 **Solution:**
 - This happens with stripped binaries
 - You can still see assembly with `disas`
 - You can still examine memory and registers
 
-## Summary
+#### Summary
 
 By completing this exercise, you've:
 1. ✅ Set up OpenOCD as a debug server
@@ -363,7 +363,7 @@ You're now ready for Week 2, where you'll:
 - Understand program flow in detail
 - Use this knowledge to modify running code
 
-## Next Steps
+#### Next Steps
 
 1. **Close GDB**: Type `quit` or `q` to exit
 2. **Close OpenOCD**: Type `Ctrl+C` in the OpenOCD terminal