topic Re: frdmk66f_lwip_udpecho_bm in Kinetis Microcontrollers

frdmk66f_lwip_udpecho_bm

randyseedle — Tue, 07 May 2019 04:00:46 GMT

I have a FRDM_64 board. And I have been trying to get frdmk66f_lwip_udpecho_bm.c to run. When I go to debug it seems to stop on line 95 of lwip_udpecho_bm.c (BOARD_BootClockRUN();). Thread 1 is running.

My PC's IP port is set to is configured as 192.168.0.100. The debug window shows:

main () at ../source/lwip_udpecho_bm.c:87
87 ethernetif_config_t fsl_enet_config0 = {

Program received signal SIGTRAP, Trace/breakpoint trap.
0x0000c7ba in HardFault_Handler () at ../source/semihost_hardfault.c:72
72 __asm( ".syntax unified\n"
tbreak main
Note: breakpoint 8 also set at pc 0x50e.
Temporary breakpoint 10 at 0x50e: file ../source/lwip_udpecho_bm.c, line 87.
monitor reset
continue
Continuing.

Temporary breakpoint 8, main () at ../source/lwip_udpecho_bm.c:87
87 ethernetif_config_t fsl_enet_config0 = {
No breakpoint number 10.

Program received signal SIGINT, Interrupt.
main () at ../source/lwip_udpecho_bm.c:87
87 ethernetif_config_t fsl_enet_config0 = {

The console shows:

SEGGER J-Link GDB Server V6.44f - Terminal output channel
Resetting target

Resetting target

--------------------------------------------------------------

C:\Users\Randy\Downloads\EchoTool-master\EchoTool-master\EchoTool\bin\Debug>echo
tool 192.168.0.102 /p udp /r 7 /d hello

Hostname 192.168.0.102 resolved as 192.168.0.102

Response time out
Response time out
Response time out
Response time out
Response time out

Statistics: Received=0, Corupted=0, Lost=5

C:\Users\Randy\Downloads\EchoTool-master\EchoTool-master\EchoTool\bin\Debug>

Re: frdmk66f_lwip_udpecho_bm

jingpan — Tue, 07 May 2019 08:52:24 GMT

Hi,

Since your code stops on BOARD_BootClockRUN() and hardfault happen, I think there may be some clock setting error. At this stage, lwip even doesn't initialized. Do you change the clock setting? If yes, you can re-config clock tree at ConfigTools->clocks. This tool make the work visualize and it can check the result.

If the problem still there, please show me how you config the clock.

Regards,

Jing

Re: frdmk66f_lwip_udpecho_bm

randyseedle — Wed, 08 May 2019 00:29:04 GMT

I did not change the clock. It is the same as the initial install.

Re: frdmk66f_lwip_udpecho_bm

jingpan — Wed, 08 May 2019 06:40:53 GMT

Hi,

You use frdmk66f_lwip_udpecho_bm as demo, but your board is frdm-k64?

Re: frdmk66f_lwip_udpecho_bm

randyseedle — Thu, 09 May 2019 00:56:48 GMT

Yes, I am using FRDM-k64 for this demo. How can I check the clock's setting in ConfigTools->clocks ? What should its

setting be normally ?

Re: frdmk66f_lwip_udpecho_bm

jingpan — Thu, 09 May 2019 01:42:12 GMT

K66's code can't run on K64. Their MCG block are different. They are different device. Please download FRDM-K64F SDK and try frdmk64f_lwip_udpecho_bm.

Regards,

Jing

Re: frdmk66f_lwip_udpecho_bm

randyseedle — Thu, 09 May 2019 19:49:27 GMT

Jing Pan:

Yes, you are correct. It works now. Thanks.

Randy