NXP FRDM-k64f ethernet AWS problem

[RenanStarke]

Good day,

I was reading a issue with NXP mdio_nxp_enet with Zephyr v3.7.0 (https://github.com/zephyrproject-rtos/zephyr/issues/76446) and I'm having a similar, but worse problem. We are using the FRDM-K64F board as a development platform and using AWS IOT sample to build our application. Unfortunately, after some random time, the PHY and LINK go down, and I suspect the CPU became without clock. The only way to restart the application is to unplug/plug to restart everything. I appreciate any help you can provide.

PHY (0) is entering autonegotiation sequence

PHY (0) autonegotiation completed

PHY 0 is up

PHY (0) Link speed 100 Mb, full duplex

I: PHY 0 is up

I: PHY (0) Link speed 100 Mb, full duplex

ethernet MAC 02:04:9f:a5:16:a2

*** Booting Zephyr OS build v3.7.0 ***

I: starting DHCPv4

I: Address[1]: 192.168.0.42

I: Subnet[1]: 255.255.255.0

I: Router[1]: 192.168.0.1

I: Lease time[1]: 86400 seconds

I: Initializing digital input pins.

I: Initializing Temperature (maxim_max31865) Sensor

I: Initializing analog voltage inputs.

I: ADCs HW counter setup done

I: Initializing analog current inputs.

I: Starting analog current inputs thread.

I: Starting analog voltage inputs thread.

Acquired time from NTP server: 1744238440

I: Setup TLS credentials

I: Resolved: 52.67.214.160:8883

MQTT event: CONNACK [0] result: 0

I: Subscribing to 1 topic(s)

MQTT event: SUBACK [7] result: 0

I: PUBLISHED on topic "sdk/test/java" [ id: 22435 qos: 0 ], payload: 343 B

(...)

I: PUBLISHED on topic "sdk/test/java" [ id: 28156 qos: 0 ], payload: 343 B

PHY 0 is down

I: Link is down <------------ After this, everything stops. Can't debug, can't flash using CMSIS DAP. Recover only with power cycle.

[Celeste_Liu]

Hello @RenanStarke ,

Thanks for your post. Which example demo you are using?

Could you please help me check whether the same error will occur if you use the baremetal AWS IOT project in Select Board | MCUXpresso SDK Builder instead of the Zephyr project?
Would it be convenient for you to tell me the detailed test steps so as to help me reproduce your problem?

BRs,

Celeste

[RenanStarke]

Hi @Celeste_Liu , thank you.

I'm using aws_iot_mqtt_sample with Zephyr 3.7.0 LTS and zephyr-sdk-0.16.8. The problem occurs when the sample code is modified to publish a static string every minute, simulating our application.

west build -b frdm_k64f    (without any modification in DTS nor prj.conf)

Although I haven't tested it with AWS using MCU Expresso, I observed that with Zephyr 4.1.0, the Ethernet connection is lost after prolonged operation, but the MCU clock and PHY remain operational.