Using PHY module DP83848 with Micropython

[abinjacob10]

How to make use of Micropython with PHY module DP83848, connected to STM32F407.
IP address need to be assigned to pyboard(STM32F407),it could be Static or DHCP.

Physical connection:
[STM32F407]---------few Jumpers ---------[DP83848]-RJ45--------------------Ethernet cable---------------------RJ45-[Laptop(Ubuntu)]

STM32F407 is already flashed with Micropython.

Any ideas are welcome!!

[brave-ulysses]

a "few jumpers" could stand some details...

to enable comms, you may need something like:
MICROPY_PY_ETH=RMII BOARD=VCC_GND_F407ZG make

this fails to build on my system:
MICROPY_PY_ETH=RMII BOARD=STM32F4DISC make

import network
lan=network.LAN()
lan.active(True)
lan.ifconfig('dhcp')

lan.ifconfig((ADDR,MASK,GWAY,DNS))

my .02 worth:
the easy button is get a nucleo-f746/f756/f767 with integrated ethernet. they all work with micropython

good luck!

[abinjacob10]

@brave-ulysses
Thank you for looking into this.

Jumper connections between STM and DP83848 should look as shown in this blog. Look for "Ethernet PHY connections"
http://blog.tkjelectronics.dk/2012/08/ethernet-on-stm32f4discovery-using-external-phy/

[brave-ulysses]

have you built a micropython version with rmii support? if so, what happens when you attempt lan setup?

[abinjacob10]

How exactly can I flash micropython with RMII support ? I did not quite follow the codes in the first message.

Till now I followed steps shown here to build the mpython board.
https://github.com/abinjacob10/Integrating-STM32F407-with-Azure-IoT-Hub.

[abinjacob10]

Corrected link:
https://github.com/abinjacob10/Integrating-STM32F407-with-Azure-IoT-Hub..git

[brave-ulysses]

link missing a '.'
azure iot hub

in the first A.5 section, replace the make command with:
BOARD=STM32F4DISC MICROPY_PY_ETH=RMII make

program per usual. i use st-flash on mint linux

st-flash write build-STM32F4DISC/firmware0.bin 0x08000000
st-flash write build-STM32F4DISC/firmware1.bin 0x08020000

[brave-ulysses]

ok - it appears some definitions are missing from the STM32F4DISC setup to enable rmii ethernet

in directory boards/STM32F4DISC

add to the end of pins.csv

PG11,PG11
PG13,PG13
PG14,PG14

add to the end of mpconfigboard.h

// Ethernet via RMII
#define MICROPY_HW_ETH_RMII_TX_EN   (pin_G11)
#define MICROPY_HW_ETH_MDC          (pin_C1)
#define MICROPY_HW_ETH_MDIO         (pin_A2)
#define MICROPY_HW_ETH_RMII_REF_CLK (pin_A1)
#define MICROPY_HW_ETH_RMII_CRS_DV  (pin_A7)
#define MICROPY_HW_ETH_RMII_RXD0    (pin_C4)
#define MICROPY_HW_ETH_RMII_RXD1    (pin_C5)
#define MICROPY_HW_ETH_RMII_TXD0    (pin_G13)
#define MICROPY_HW_ETH_RMII_TXD1    (pin_G14)

add to the end of mpconfigboard.mk

# MicroPython settings
MICROPY_PY_LWIP = 1
MICROPY_PY_USSL = 1
MICROPY_SSL_MBEDTLS = 1

build with
BOARD=STM32F4DISC make

load fw with preferred method
BOARD=STM32F4DISC make deploy-stlink

this fails because i don't have the phy hardware:

>>> 
MPY: sync filesystems
MPY: soft reboot
MicroPython v1.19.1-608-gb52fe52d3-dirty on 2022-12-04; F4DISC with STM32F407
Type "help()" for more information.
>>> import network
>>> lan=network.LAN()
>>> lan.active(True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 110] ETIMEDOUT
>>> 

again, i'd recommend one of the nucleo boards mentioned above

good luck!

[abinjacob10]

I was missing a single jumper, will be working on this very soon and reply back.

Thank you @brave-ulysses

[abinjacob10]

@brave-ulysses

First I feel there was no need to edit pins.csv
Because, In my board there is no PG11, PG13, PG14 pins, but there are PB pins which are already there in .csv file

Few corrections that i felt was required

// Ethernet via RMII
#define MICROPY_HW_ETH_RMII_TX_EN   (pin_G11)        >> **pin_B11**(only PB port available)
#define MICROPY_HW_ETH_MDC          (pin_C1)                
#define MICROPY_HW_ETH_MDIO         (pin_A2)
#define MICROPY_HW_ETH_RMII_REF_CLK (pin_A1)
#define MICROPY_HW_ETH_RMII_CRS_DV  (pin_A7)
#define MICROPY_HW_ETH_RMII_RXD0    (pin_C4)
#define MICROPY_HW_ETH_RMII_RXD1    (pin_C5)
#define MICROPY_HW_ETH_RMII_TXD0    (pin_G13)        >> **pin_B12**(as per the diagram from blog)
#define MICROPY_HW_ETH_RMII_TXD1    (pin_G14)`       >> **pin_B13**(as per the diagram from blog)

I edited this file as per above corrections:
/micropython-1.19.1/ports/stm32/boards/STM32F4DISC/mpconfigboard.h

Used settings as per your post:
/micropython-1.19.1/ports/stm32/boards/STM32F4DISC/mpconfigboard.mk

After these corrections, I proceeded to build.

[abinjacob10]

Build process, could see a an error about usocket, I avoided it for now:

2nd attempt

abin@ThinkPad-P14s-Gen-2a:~/Downloads/micropython-1.19.1/ports/stm32$ MICROPY_PY_ETH=RMII BOARD=STM32F4DISC make
Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity.
GEN build-STM32F4DISC/genhdr/qstr.i.last
GEN build-STM32F4DISC/genhdr/qstr.split
GEN build-STM32F4DISC/genhdr/qstrdefs.collected.h
QSTR not updated
GEN build-STM32F4DISC/genhdr/qstrdefs.generated.h
GEN build-STM32F4DISC/genhdr/moduledefs.split
GEN build-STM32F4DISC/genhdr/moduledefs.collected
Module registrations not updated
GEN build-STM32F4DISC/genhdr/compressed.split
GEN build-STM32F4DISC/genhdr/compressed.collected
Compressed data not updated
CC ../../py/mpstate.c
CC ../../py/nlr.c
CC ../../py/nlrx86.c
CC ../../py/nlrx64.c
CC ../../py/nlrthumb.c
CC ../../py/nlraarch64.c
CC ../../py/nlrpowerpc.c
CC ../../py/nlrxtensa.c
CC ../../py/nlrsetjmp.c
CC ../../py/malloc.c
CC ../../py/gc.c
CC ../../py/pystack.c
CC ../../py/qstr.c
CC ../../py/vstr.c
CC ../../py/mpprint.c
CC ../../py/unicode.c
CC ../../py/mpz.c
CC ../../py/reader.c
CC ../../py/lexer.c
CC ../../py/parse.c
CC ../../py/scope.c
CC ../../py/compile.c
CC ../../py/emitcommon.c
CC ../../py/emitbc.c
CC ../../py/asmbase.c
CC ../../py/asmx64.c
CC ../../py/emitnx64.c
CC ../../py/asmx86.c
CC ../../py/emitnx86.c
CC ../../py/asmthumb.c
CC ../../py/emitnthumb.c
CC ../../py/emitinlinethumb.c
CC ../../py/asmarm.c
CC ../../py/emitnarm.c
CC ../../py/asmxtensa.c
CC ../../py/emitnxtensa.c
CC ../../py/emitinlinextensa.c
CC ../../py/emitnxtensawin.c
CC ../../py/formatfloat.c
CC ../../py/parsenumbase.c
CC ../../py/parsenum.c
CC ../../py/emitglue.c
CC ../../py/persistentcode.c
CC ../../py/runtime.c
CC ../../py/runtime_utils.c
CC ../../py/scheduler.c
CC ../../py/nativeglue.c
CC ../../py/pairheap.c
CC ../../py/stackctrl.c
CC ../../py/argcheck.c
CC ../../py/warning.c
CC ../../py/profile.c
CC ../../py/map.c
CC ../../py/obj.c
CC ../../py/objarray.c
CC ../../py/objattrtuple.c
CC ../../py/objbool.c
CC ../../py/objboundmeth.c
CC ../../py/objcell.c
CC ../../py/objclosure.c
CC ../../py/objcomplex.c
CC ../../py/objdeque.c
CC ../../py/objdict.c
CC ../../py/objenumerate.c
CC ../../py/objexcept.c
CC ../../py/objfilter.c
CC ../../py/objfloat.c
CC ../../py/objfun.c
CC ../../py/objgenerator.c
CC ../../py/objgetitemiter.c
CC ../../py/objint.c
CC ../../py/objint_longlong.c
CC ../../py/objint_mpz.c
CC ../../py/objlist.c
CC ../../py/objmap.c
CC ../../py/objmodule.c
CC ../../py/objobject.c
CC ../../py/objpolyiter.c
CC ../../py/objproperty.c
CC ../../py/objnone.c
CC ../../py/objnamedtuple.c
CC ../../py/objrange.c
CC ../../py/objreversed.c
CC ../../py/objset.c
CC ../../py/objsingleton.c
CC ../../py/objslice.c
CC ../../py/objstr.c
CC ../../py/objstrunicode.c
CC ../../py/objstringio.c
CC ../../py/objtuple.c
CC ../../py/objtype.c
CC ../../py/objzip.c
CC ../../py/opmethods.c
CC ../../py/sequence.c
CC ../../py/stream.c
CC ../../py/binary.c
CC ../../py/builtinimport.c
CC ../../py/builtinevex.c
CC ../../py/builtinhelp.c
CC ../../py/modarray.c
CC ../../py/modbuiltins.c
CC ../../py/modcollections.c
CC ../../py/modgc.c
CC ../../py/modio.c
CC ../../py/modmath.c
CC ../../py/modcmath.c
CC ../../py/modmicropython.c
CC ../../py/modstruct.c
CC ../../py/modsys.c
CC ../../py/moduerrno.c
CC ../../py/modthread.c
CC ../../py/vm.c
CC ../../py/bc.c
CC ../../py/showbc.c
CC ../../py/repl.c
CC ../../py/smallint.c
CC ../../py/frozenmod.c
CC ../../extmod/moduasyncio.c
CC ../../extmod/moductypes.c
CC ../../extmod/modujson.c
CC ../../extmod/moduos.c
CC ../../extmod/modure.c
CC ../../extmod/moduzlib.c
CC ../../extmod/moduheapq.c
CC ../../extmod/modutimeq.c
CC ../../extmod/moduhashlib.c
CC ../../extmod/moducryptolib.c
CC ../../extmod/modubinascii.c
CC ../../extmod/virtpin.c
CC ../../extmod/machine_bitstream.c
CC ../../extmod/machine_mem.c
CC ../../extmod/machine_pinbase.c
CC ../../extmod/machine_signal.c
CC ../../extmod/machine_pulse.c
CC ../../extmod/machine_pwm.c
CC ../../extmod/machine_i2c.c
CC ../../extmod/machine_spi.c
CC ../../extmod/modbluetooth.c
CC ../../extmod/modussl_axtls.c
CC ../../extmod/modussl_mbedtls.c
CC ../../extmod/moduplatform.c
CC ../../extmod/modurandom.c
CC ../../extmod/moduselect.c
CC ../../extmod/moduwebsocket.c
CC ../../extmod/modwebrepl.c
CC ../../extmod/modframebuf.c
CC ../../extmod/vfs.c
CC ../../extmod/vfs_blockdev.c
CC ../../extmod/vfs_reader.c
CC ../../extmod/vfs_posix.c
CC ../../extmod/vfs_posix_file.c
CC ../../extmod/vfs_fat.c
CC ../../extmod/vfs_fat_diskio.c
CC ../../extmod/vfs_fat_file.c
CC ../../extmod/vfs_lfs.c
CC ../../extmod/utime_mphal.c
CC ../../extmod/uos_dupterm.c
CC ../../shared/libc/abort_.c
CC ../../shared/libc/printf.c
CC build-STM32F4DISC/frozen_content.c
CC ../../shared/netutils/dhcpserver.c
CC ../../shared/netutils/netutils.c
CC ../../shared/netutils/trace.c
CC ../../shared/readline/readline.c
CC ../../shared/runtime/gchelper_native.c
CC ../../shared/runtime/interrupt_char.c
CC ../../shared/runtime/mpirq.c
CC ../../shared/runtime/pyexec.c
CC ../../shared/runtime/stdout_helpers.c
CC ../../shared/runtime/sys_stdio_mphal.c
CC ../../shared/timeutils/timeutils.c
CC ../../extmod/modonewire.c
CC ../../extmod/modnetwork.c
CC ../../extmod/modusocket.c
CC ../../drivers/bus/softspi.c
CC ../../drivers/bus/softqspi.c
CC ../../drivers/memory/spiflash.c
CC ../../drivers/dht/dht.c
CC usbdev/core/src/usbd_core.c
CC usbdev/core/src/usbd_ctlreq.c
CC usbdev/core/src/usbd_ioreq.c
CC usbdev/class/src/usbd_cdc_msc_hid.c
CC usbdev/class/src/usbd_msc_bot.c
CC usbdev/class/src/usbd_msc_scsi.c
CC boardctrl.c
CC main.c
CC stm32_it.c
CC usbd_conf.c
CC usbd_desc.c
CC usbd_cdc_interface.c
CC usbd_hid_interface.c
CC usbd_msc_interface.c
CC mphalport.c
CC mpnetworkport.c
CC mpthreadport.c
CC irq.c
CC pendsv.c
CC systick.c
CC softtimer.c
CC powerctrl.c
CC powerctrlboot.c
CC rfcore.c
CC pybthread.c
CC factoryreset.c
CC timer.c
CC led.c
CC pin.c
CC pin_defs_stm32.c
CC pin_named_pins.c
CC bufhelper.c
CC dma.c
CC i2c.c
CC pyb_i2c.c
CC spi.c
CC pyb_spi.c
CC qspi.c
CC uart.c
CC ulpi.c
CC can.c
CC fdcan.c
CC pyb_can.c
CC usb.c
CC wdt.c
CC eth.c
CC gccollect.c
CC help.c
CC machine_adc.c
CC machine_bitstream.c
CC machine_i2c.c
CC machine_i2s.c
CC machine_spi.c
CC machine_timer.c
CC machine_uart.c
CC modmachine.c
CC modpyb.c
CC modstm.c
CC modutime.c
CC network_lan.c
CC extint.c
CC usrsw.c
CC rng.c
CC rtc.c
CC flash.c
CC flashbdev.c
CC spibdev.c
CC storage.c
CC sdcard.c
CC sdram.c
CC fatfs_port.c
CC lcd.c
CC accel.c
CC servo.c
CC dac.c
CC adc.c
CC system_stm32.c
CC ../../lib/oofatfs/ff.c
CC ../../lib/oofatfs/ffunicode.c
CC ../../lib/mbedtls/library/aes.c
CC ../../lib/mbedtls/library/aesni.c
CC ../../lib/mbedtls/library/arc4.c
CC ../../lib/mbedtls/library/asn1parse.c
CC ../../lib/mbedtls/library/asn1write.c
CC ../../lib/mbedtls/library/base64.c
CC ../../lib/mbedtls/library/bignum.c
CC ../../lib/mbedtls/library/blowfish.c
CC ../../lib/mbedtls/library/camellia.c
CC ../../lib/mbedtls/library/ccm.c
CC ../../lib/mbedtls/library/certs.c
CC ../../lib/mbedtls/library/chacha20.c
CC ../../lib/mbedtls/library/chachapoly.c
CC ../../lib/mbedtls/library/cipher.c
CC ../../lib/mbedtls/library/cipher_wrap.c
CC ../../lib/mbedtls/library/cmac.c
CC ../../lib/mbedtls/library/ctr_drbg.c
CC ../../lib/mbedtls/library/debug.c
CC ../../lib/mbedtls/library/des.c
CC ../../lib/mbedtls/library/dhm.c
CC ../../lib/mbedtls/library/ecdh.c
CC ../../lib/mbedtls/library/ecdsa.c
CC ../../lib/mbedtls/library/ecjpake.c
CC ../../lib/mbedtls/library/ecp.c
CC ../../lib/mbedtls/library/ecp_curves.c
CC ../../lib/mbedtls/library/entropy.c
CC ../../lib/mbedtls/library/entropy_poll.c
CC ../../lib/mbedtls/library/gcm.c
CC ../../lib/mbedtls/library/havege.c
CC ../../lib/mbedtls/library/hmac_drbg.c
CC ../../lib/mbedtls/library/md2.c
CC ../../lib/mbedtls/library/md4.c
CC ../../lib/mbedtls/library/md5.c
CC ../../lib/mbedtls/library/md.c
CC ../../lib/mbedtls/library/md_wrap.c
CC ../../lib/mbedtls/library/oid.c
CC ../../lib/mbedtls/library/padlock.c
CC ../../lib/mbedtls/library/pem.c
CC ../../lib/mbedtls/library/pk.c
CC ../../lib/mbedtls/library/pkcs11.c
CC ../../lib/mbedtls/library/pkcs12.c
CC ../../lib/mbedtls/library/pkcs5.c
CC ../../lib/mbedtls/library/pkparse.c
CC ../../lib/mbedtls/library/pk_wrap.c
CC ../../lib/mbedtls/library/pkwrite.c
CC ../../lib/mbedtls/library/platform.c
CC ../../lib/mbedtls/library/platform_util.c
CC ../../lib/mbedtls/library/poly1305.c
CC ../../lib/mbedtls/library/ripemd160.c
CC ../../lib/mbedtls/library/rsa.c
CC ../../lib/mbedtls/library/rsa_internal.c
CC ../../lib/mbedtls/library/sha1.c
CC ../../lib/mbedtls/library/sha256.c
CC ../../lib/mbedtls/library/sha512.c
CC ../../lib/mbedtls/library/ssl_cache.c
CC ../../lib/mbedtls/library/ssl_ciphersuites.c
CC ../../lib/mbedtls/library/ssl_cli.c
CC ../../lib/mbedtls/library/ssl_cookie.c
CC ../../lib/mbedtls/library/ssl_srv.c
CC ../../lib/mbedtls/library/ssl_ticket.c
CC ../../lib/mbedtls/library/ssl_tls.c
CC ../../lib/mbedtls/library/timing.c
CC ../../lib/mbedtls/library/x509.c
CC ../../lib/mbedtls/library/x509_create.c
CC ../../lib/mbedtls/library/x509_crl.c
CC ../../lib/mbedtls/library/x509_crt.c
CC ../../lib/mbedtls/library/x509_csr.c
CC ../../lib/mbedtls/library/x509write_crt.c
CC ../../lib/mbedtls/library/x509write_csr.c
CC ../../lib/mbedtls/library/xtea.c
CC ../../extmod/modlwip.c
CC ../../lib/lwip/src/apps/mdns/mdns.c
CC ../../lib/lwip/src/core/def.c
CC ../../lib/lwip/src/core/dns.c
CC ../../lib/lwip/src/core/inet_chksum.c
CC ../../lib/lwip/src/core/init.c
CC ../../lib/lwip/src/core/ip.c
CC ../../lib/lwip/src/core/mem.c
CC ../../lib/lwip/src/core/memp.c
CC ../../lib/lwip/src/core/netif.c
CC ../../lib/lwip/src/core/pbuf.c
CC ../../lib/lwip/src/core/raw.c
CC ../../lib/lwip/src/core/stats.c
CC ../../lib/lwip/src/core/sys.c
CC ../../lib/lwip/src/core/tcp.c
CC ../../lib/lwip/src/core/tcp_in.c
CC ../../lib/lwip/src/core/tcp_out.c
CC ../../lib/lwip/src/core/timeouts.c
CC ../../lib/lwip/src/core/udp.c
CC ../../lib/lwip/src/core/ipv4/autoip.c
CC ../../lib/lwip/src/core/ipv4/dhcp.c
CC ../../lib/lwip/src/core/ipv4/etharp.c
CC ../../lib/lwip/src/core/ipv4/icmp.c
CC ../../lib/lwip/src/core/ipv4/igmp.c
CC ../../lib/lwip/src/core/ipv4/ip4_addr.c
CC ../../lib/lwip/src/core/ipv4/ip4.c
CC ../../lib/lwip/src/core/ipv4/ip4_frag.c
CC ../../lib/lwip/src/core/ipv6/dhcp6.c
CC ../../lib/lwip/src/core/ipv6/ethip6.c
CC ../../lib/lwip/src/core/ipv6/icmp6.c
CC ../../lib/lwip/src/core/ipv6/inet6.c
CC ../../lib/lwip/src/core/ipv6/ip6_addr.c
CC ../../lib/lwip/src/core/ipv6/ip6.c
CC ../../lib/lwip/src/core/ipv6/ip6_frag.c
CC ../../lib/lwip/src/core/ipv6/mld6.c
CC ../../lib/lwip/src/core/ipv6/nd6.c
CC ../../lib/lwip/src/netif/ethernet.c
CC mbedtls/mbedtls_port.c
CC build-STM32F4DISC/pins_STM32F4DISC.c
LINK build-STM32F4DISC/firmware.elf
arm-none-eabi-ld: build-STM32F4DISC/py/objmodule.o:(.rodata.mp_builtin_module_table+0xd4): undefined reference to `mp_module_usocket'
make: *** [Makefile:691: build-STM32F4DISC/firmware.elf] Error 1

[abinjacob10]

While trying network.LAN(), object was not found by uPython.
Using tab button after network. gives available objects(we could see AP_IF, STA_IF and route, but no LAN)

abin@ThinkPad-P14s-Gen-2a:~/Downloads/micropython-1.19.1/ports/stm32$ rshell 
Connecting to /dev/ttyACM2 (buffer-size 512)...
Trying to connect to REPL  connected
Retrieving sysname ... pyboard
Testing if sys.stdin.buffer exists ... Y
Retrieving root directories ... /flash/
Setting time ... Dec 06, 2022 10:06:30
Evaluating board_name ... pyboard
Retrieving time epoch ... Jan 01, 2000
Welcome to rshell. Use Control-D (or the exit command) to exit rshell.
/home/abin/Downloads/micropython-1.19.1/ports/stm32> repl
Entering REPL. Use Control-X to exit.
>
MicroPython v1.19.1 on 2022-10-14; F4DISC with STM32F407
Type "help()" for more information.
>>> 
>>> import network
>>> help(network.
AP_IF           STA_IF          route
>>> lan=network.
AP_IF           STA_IF          route
>>> lan=network.LAN()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'LAN'
>>> 

[abinjacob10]

What are the corrections needed?

[brave-ulysses]

hi abin,

starting with a clean slate, these commands appear to work

good luck,

clay

cd /tmp
git clone git@github.com:micropython/micropython.git
cd micropython/
git submodule update --init
make -C mpy-cross/
cd ports/stm32/
make submodules

cat <<EOF >> boards/STM32F4DISC/mpconfigboard.mk

# MicroPython settings
MICROPY_PY_LWIP = 1
MICROPY_PY_USSL = 1
MICROPY_SSL_MBEDTLS = 1
EOF


cat <<EOF >>  boards/STM32F4DISC/mpconfigboard.h

// Ethernet via RMII
#define MICROPY_HW_ETH_RMII_TX_EN   (pin_B11)
#define MICROPY_HW_ETH_MDC          (pin_C1)                
#define MICROPY_HW_ETH_MDIO         (pin_A2)
#define MICROPY_HW_ETH_RMII_REF_CLK (pin_A1)
#define MICROPY_HW_ETH_RMII_CRS_DV  (pin_A7)
#define MICROPY_HW_ETH_RMII_RXD0    (pin_C4)
#define MICROPY_HW_ETH_RMII_RXD1    (pin_C5)
#define MICROPY_HW_ETH_RMII_TXD0    (pin_B12)
#define MICROPY_HW_ETH_RMII_TXD1    (pin_B13)
EOF

BOARD=STM32F4DISC make

BOARD=STM32F4DISC make deploy-stlink

# hit reset button

rshell
repl

>>> import network
>>> lan=network.LAN()
>>> lan.active()
True
>>> lan.isconnected()
False
>>> 

[abinjacob10]

Some success!!

As suggested, I tried the fresh build, used the same dfu-util to flash the firmware though, not st-link method.

After flashing,

>>> import network
>>> lan=network.
AP_IF           LAN             STA_IF          route

>>> lan.status()
1
>>> lan.active()
True
>>> lan.isconnected()
False
>>> 

I have not built RMII into pyboard yet. Do I need to do it after the previous flash ?

MICROPY_PY_ETH=RMII BOARD=STM32F4DISC make

[brave-ulysses]

you should be ready to go

MICROPY_PY_ETH=RMII is not needed: i used this on another board several years back...

can you plug into a switch and get a link indication?

what does lan.ifconfig() show?

[abinjacob10]

>>> lan.ifconfig()
('0.0.0.0', '0.0.0.0', '0.0.0.0', '0.0.0.0')
>>> 

[abinjacob10]

I don't have a switch as of now.
Connection is same as shown before.

[STM32F407]---------Jumpers ---------[DP83848]-RJ45--------------------Ethernet cable---------------------RJ45-[Laptop(Ubuntu)]

I have statically configured ethernet port on PC
IP 172.16.32.1 /29

[brave-ulysses]

do you have a dhcp server on the segment?
does the ubuntu interface show RUNNING flag

ADDR="172.16.32.2"
MASK="255.255.255.248"
GWAY=ADDR
DNS=ADDR
lan.ifconfig((ADDR,MASK,GWAY,DNS))

try pinging from computer

[abinjacob10]

Looks like NIC on Ubuntu-PC is not getting MAC of the board. Its trying the ARP.

pyboard is configured as:

>> lan.ifconfig()
('172.16.32.2', '255.255.255.248', '172.16.32.2', '172.16.32.2')

abin@ThinkPad-P14s-Gen-2a:/tmp/micropython/ports/stm32$ ping 172.16.32.2
PING 172.16.32.2 (172.16.32.2) 56(84) bytes of data.
From 172.16.32.1 icmp_seq=1 Destination Host Unreachable
From 172.16.32.1 icmp_seq=2 Destination Host Unreachable
From 172.16.32.1 icmp_seq=3 Destination Host Unreachable
From 172.16.32.1 icmp_seq=4 Destination Host Unreachable
From 172.16.32.1 icmp_seq=8 Destination Host Unreachable
From 172.16.32.1 icmp_seq=11 Destination Host Unreachable
From 172.16.32.1 icmp_seq=12 Destination Host Unreachable
^Z
[2]+  Stopped                 ping 172.16.32.2
abin@ThinkPad-P14s-Gen-2a:/tmp/micropython/ports/stm32$ ping 172.16.32.2 -c 1
PING 172.16.32.2 (172.16.32.2) 56(84) bytes of data.
From 172.16.32.1 icmp_seq=1 Destination Host Unreachable

--- 172.16.32.2 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

[abinjacob10]

ARP broadcast tried by PC's NIC

[abinjacob10]

There is no DHCP server configured on PC.
What is Ubuntu running flag on interface?

How to let Ubuntu know STM32's MAC ?
In this video, looks like he has explicitly mentioned MAC of STM.

https://www.youtube.com/watch?v=EjOinds1f18&ab_channel=TKJElectronics.

Watch at time: 2:48

[abinjacob10]

When I ping a single packet(when it's ARPing) from Ubuntu-PC all the way to board, I see LED blink on the DP83848 RJ45 connector.
This means the PHY module is powered ON correctly.

172.16.32.2/29                                                    172.16.32.1 /29
STM----------------PHY-module-(RJ-45)--------------------(RJ-45)-Ubuntu-PC

[brave-ulysses]

RUNNING flag indicates exchanging link pulses with another device. a first check for wiring or mdi/mdi-x issues

your arp does not look right. i'd expect 172.16.32.2 to be in the packet

7 2.897299006 ASRockIn_fc:3f:ca → Broadcast    ARP 42 Who has 172.16.32.2? Tell 172.16.32.1

what does ifconfig show for your ubuntu interface?

[abinjacob10]

ifconfig on Ubuntu

enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.32.1  netmask 255.255.255.248  broadcast 172.16.32.7
        inet6 fe80::5b44:b103:1224:808f  prefixlen 64  scopeid 0x20<link>
        ether 88:a4:c2:6f:d5:3b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2077  bytes 274457 (274.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[brave-ulysses]

can you show the results from linux for

ping 172.16.32.2
arping -I enp5s0 172.16.32.2

on my nucleo boards, i do
lan.active(True)

[abinjacob10]

ping trials

abin@ThinkPad-P14s-Gen-2a:/tmp/micropython/ports/stm32$ ping 172.16.32.2
PING 172.16.32.2 (172.16.32.2) 56(84) bytes of data.
From 172.16.32.1 icmp_seq=1 Destination Host Unreachable
From 172.16.32.1 icmp_seq=2 Destination Host Unreachable
From 172.16.32.1 icmp_seq=3 Destination Host Unreachable
From 172.16.32.1 icmp_seq=4 Destination Host Unreachable
From 172.16.32.1 icmp_seq=5 Destination Host Unreachable
From 172.16.32.1 icmp_seq=6 Destination Host Unreachable
From 172.16.32.1 icmp_seq=7 Destination Host Unreachable
From 172.16.32.1 icmp_seq=8 Destination Host Unreachable
From 172.16.32.1 icmp_seq=9 Destination Host Unreachable
^C
--- 172.16.32.2 ping statistics ---
11 packets transmitted, 0 received, +9 errors, 100% packet loss, time 10241ms
pipe 4

Timedout

abin@ThinkPad-P14s-Gen-2a:/tmp/micropython/ports/stm32$ sudo arping -I enp5s0 172.16.32.2
ARPING 172.16.32.2
Timeout
Timeout
Timeout
Timeout
Timeout
Timeout
Timeout
Timeout
Timeout
Timeout
^Z
[3]+  Stopped                 sudo arping -I enp5s0 172.16.32.2

[brave-ulysses]

also, verify mask - i'm was octet off on the 248 (edited...)

looks like you have it correct: 255.255.255.248

[abinjacob10]

Yes subnet mask is fine.

[brave-ulysses]

does your wireshark trace show 172.16.32.2 in the arp request?

it may be time to start rechecking wiring

[abinjacob10]

Wireshark captures:

[brave-ulysses]

trace looks correct. at this point, i'd revisit the wiring/pin definitions

[abinjacob10]

LED on PHY module blinks when it gets each packet from PC.

[abinjacob10]

DO we need to define, driver objects.

https://docs.micropython.org/en/latest/library/network.LAN.html?highlight=network%20lan

There is some reference shown here to PHY_DP83848

[brave-ulysses]

not sure. i do not do that for the nucleo boards - could be predefined

not sure where PHY_DP83848 definition is
lan=network.LAN(0, phy_type=network.LAN.PHY_DP83848, phy_addr=1, ref_clk_mode=machine.Pin.cpu.A1)

[abinjacob10]

In the bottom of link, it says

_Specific LAN class implementations¶

On the mimxrt port, suitable values for the phy_type constructor argument are: PHY_KSZ8081, PHY_DP83825, PHY_DP83848, PHY_LAN8720, PHY_RTL8211F._

[brave-ulysses]

there are a few DP83848 references in other ports. it looks like you may be in charge of phy setup if you want to continue with the dp83848

what does lan.active(True) return

if it does not timeout, i'd guess that you are talking to the phy

>>> lan.active(True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 110] ETIMEDOUT
>>> 

[abinjacob10]

It is not timing out.

Return key returns nothing

>>> lan.active(True)
>>> lan.active(True)
>>> 

[abinjacob10]

But below shows False

lan.isconnected()
False

[brave-ulysses]

lan.status() ?

>>> lan.status()
1
>>> 

[abinjacob10]

>>> lan.status()
3

[brave-ulysses]

this is on a nucleo board...

check your output with wireshark

>>> import network
>>> lan=network.LAN()
>>> lan.status()
1
>>> lan.active(True)
>>> lan.status()
3
>>> lan.ifconfig()
('174.0.0.74', '255.255.255.0', '174.0.0.1', '192.168.1.254')
>>> import socket
>>> addr = socket.getaddrinfo('micropython.org', 80)[0][-1]
>>> addr
('176.58.119.26', 80)
>>> 

[abinjacob10]

Something is strange about the status() with my connections. As a result socket didn't work.
What are the meaning of return codes 3 and 2 ?

lan.status()
3
lan.active(True)
lan.status()
2

[brave-ulysses]

not sure. i did some digging and, without a parameter, it is the link status. haven't found a meaning for the values. may require a dive into the datasheets

stm32/eth.c calls out values for lan8742 phy. you may be able to replace them with appropriate dp83848 values

can you move from the f4disco board?

[abinjacob10]

OK, i should stop here then with F4 board

[RichardWei]

Hi, I have a similar problem, did you solve it in the end with stm32f407?

[brave-ulysses]

a nucleo 767 board should let you get the network up quickly and move onto the meat of the project

i used your current hw combination ~10 years ago with nuttxos. it looks like there was some attempt to port that work to micropython

good luck

[abinjacob10]

Hi, I could not solve it. Try if you have time, and less resources, you could get it. Good luck!

…

On Fri, 21 Jun 2024, 16:19 RichardWei, ***@***.***> wrote: Hi, I have a similar problem, did you solve it in the end with stm32f407? — Reply to this email directly, view it on GitHub <#10141 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF3CEGBIPUWKI2EQ3ILV4HTZIRAADAVCNFSM6AAAAABJWFPTR2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNBRGIYTI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[RichardWei]

Hi, I could not solve it. Try if you have time, and less resources, you could get it. Good luck!
…
On Fri, 21 Jun 2024, 16:19 RichardWei, @.> wrote: Hi, I have a similar problem, did you solve it in the end with stm32f407? — Reply to this email directly, view it on GitHub <#10141 (reply in thread)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF3CEGBIPUWKI2EQ3ILV4HTZIRAADAVCNFSM6AAAAABJWFPTR2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNBRGIYTI . You are receiving this because you authored the thread.Message ID: @. com>

@abinjacob10 ,I have solved my problem, thanks @robert-hh‘s help, If you need it, please refer to the following post,15325