---
lwip.py | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/lwip.py b/lwip.py
index 84eef2c..d806b64 100644
--- a/lwip.py
+++ b/lwip.py
@@ -92,6 +92,17 @@ common_source_files = [
'rtemslwip/bsd_compat/rtems-kernel-program.c'
]
+stm32f4_drv_incl = [
This patch adds ST's Ethernet and lwIP port and DP83848 driver. The
files are generated using STM32CubeIDE with STM32F4 Cube FW v1.27.1,
under no RTOS mode.
---
stm32/driver/dp83848.c | 664 +
stm32/driver/dp83848.h | 436
stm32/ethernet
---
rtemslwip/stm32f4/lwipopts.h | 24 ++-
rtemslwip/stm32f4/netstart.c | 29 +++-
rtemslwip/stm32f4/stm32f4_lwip.c | 14 ++
rtemslwip/stm32f4/stm32f4_lwip.h | 9 +
stm32/ethernetif.c | 288 +--
stm32/ethernetif.h | 14 +-
stm32
This patch set aims to port RTEMS lwIP for STM32F4 BSP. It also contains
generic drivers for STM32 chips in general. It is tested with a TCP echo
server application on STM32F407 Discovery Board.
Prerequisite: this patch set requires my STM32F4 patches to be applied
because it uses STM32 HAL.
Duc
---
rtemslwip/stm32f4/lwipopts.h | 141 +++
rtemslwip/stm32f4/netstart.c | 52 +
2 files changed, 193 insertions(+)
create mode 100644 rtemslwip/stm32f4/lwipopts.h
create mode 100644 rtemslwip/stm32f4/netstart.c
diff --git a/rtemslwip/stm32f4/lwipopt
Hi Noor,Nice blog entry on the JTAG setup. I ordered the FT232H board like yours to see if I can get the same setup working. I have my Pi 4 running the bare metal OS examples, and I have built your branch, so I hope to start looking at the code.What needs to be in the MMU table? I see different ent