renet/ENC424J600
10
1
Fork 1
Code Issues 3 Pull Requests 1 Projects Releases Wiki Activity
renet driver for the ENC424J600 SPI Ethernet controller
5 Commits 6 Branches 0 Tags 206 KiB
Rust 83.7%
Nix 13.8%
Shell 1.9%
GDB 0.6%
6b9f58a98f
Go to file
Harry Ho 6b9f58a98f Add tx_stm32f407 example
2020-06-18 15:06:55 +08:00
.cargo Add tx_stm32f407 example 2020-06-18 15:06:55 +08:00
examples Add tx_stm32f407 example 2020-06-18 15:06:55 +08:00
src Add packet TX 2020-06-18 11:09:39 +08:00
Cargo.lock Add tx_stm32f407 example 2020-06-18 15:06:55 +08:00
Cargo.toml Add tx_stm32f407 example 2020-06-18 15:06:55 +08:00
memory.x Add tx_stm32f407 example 2020-06-18 15:06:55 +08:00
openocd.gdb Add tx_stm32f407 example 2020-06-18 15:06:55 +08:00
README.md Add tx_stm32f407 example 2020-06-18 15:06:55 +08:00

README.md

ENC424J600 Driver

Examples

Endless Pinging - tx_stm32f407

This program demonstrates the Ethernet TX capability on an STM32F407 board connected to an ENC424J600 module via SPI. Once loaded and initialised, a specific ping packet is sent (broadcasted) every 100ms. Such a packet has the following properties:

  • Destination MAC Address: ff-ff-ff-ff-ff-ff
  • Source MAC Address: 08-60-6e-44-42-95
  • Destination IP Address: 192.168.1.231
  • Source IP Address: 192.168.1.100
  • Frame Length in Bytes: 64

Note that this program uses ITM for logging output.

How-to

  1. Prepare the Rust and Cargo environment for building and running the program on STM32F4xx Cortex-M platforms.

  2. Install itm on Cargo:

    cargo install itm

    If necessary, add your installation location (~/.cargo/bin by default) to $PATH.

  3. Connect your STM32F407 device to the computer. Without changing any code, you may use an STLink V2 debugger.

  4. Run OpenOCD with the appropriate configuration files (e.g. interface/stlink-v2.cfg, target/stm32f4x.cfg).

  5. With OpenOCD running, build and run this program:

    cargo run --release --example=tx_stm32f407 --features=stm32f407

    Use appropriate GDB commands such as c for continuing.

  6. On a separate console window, monitor and observe the ITM output, which is located at the same directory as you started OpenOCD:

    itmdump -f itm.log -F