Auto IP sets after reboot cmd execute in i.MX8MM EVK

[sreedhar_appala]

Hi,

I am working with IMX8M Mini EVK and yocto project build details:

We are working remotely by connecting through ssh client terminal

Build Configuration:
BB_VERSION = "1.38.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "imx8mmevk"
DISTRO = "fsl-imx-xwayland"
DISTRO_VERSION = "4.14-sumo"
TUNE_FEATURES = "aarch64"
TARGET_FPU = ""

I tried to program the ecspi2 pad mux control registers using the memtrol

./memtool -32 0x30330204 = 0x0 

./memtool -32 0x30330208 = 0x0

./memtool -32 0x3033020C = 0x0

./memtool -32 0x30330210 = 0x0

It is success,

then i tried running the mxc_spi_test1.out test app for spi test.

It was failure:

root@imx8mmevk:~# ./mxc_spi_test1.out -D 2 -s 1000000 -b 8 E6E0

---- Running < ./mxc_spi_test1.out > test ----

Execute data transfer test: 2 4 E6E0

Error:cannot open device (Maybe not present in your board?)

After this to check the bootup logs for spi probe log, I executed the reboot command, t

the board booted but the board is acquiring the Auto IP.

I am attaching the log, please let me know your suggestions to get the proper ipv4 address.

root@imx8mmevk:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:9f:06:3f:4d
inet addr:169.254.171.230 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: 2400:3c00:5:1188:9b97:6100:9ef7:5a3b/64 Scope:Global
inet6 addr: fe80::204:9fff:fe06:3f4d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:3302 errors:0 dropped:0 overruns:0 frame:0
TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:279760 (273.2 KiB) TX bytes:42530 (41.5 KiB)

root@imx8mmevk:~# ./memtool -32 0x30be0000 4
E
Reading 0x4 count starting at [ 54.003423] Synchronous External Abort: synchronous external abort (0x92000210) at 0x0000ffffa21e8000
address 0x30BE0000

[ 54.015623] Unhandled fault: synchronous external abort (0x92000210) at 0x0000ffffa21e8000
[ 54.025802] Mem abort info:
[ 54.028644] Exception class = DABT (lower EL), IL = 32 bits
[ 54.034427] SET = 0, FnV = 0
[ 54.037495] EA = 1, S1PTW = 0
[ 54.040693] Data abort info:
[ 54.043622] ISV = 0, ISS = 0x00000210
[ 54.047494] CM = 0, WnR = 0
[ 54.050586] audit: type=1701 audit(1589528207.456:3): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=3936 comm="memtool" exe="/home/root/memtool" sig=7 res=1
Bus error (core dumped)

Thank you,

Sreedhar

[weidong_sun]

Hello Sreedhar,

   You can connect ethernet of i.MX8MM-EVK board to Router , then run ifconfig to check if IP address has been assigned.

   If you want a static IP, you can use systemd to get the purpose.

Have a nice day!

B.R,

Weidong

[sreedhar_appala]

Hi Weidong,

We can't connect to the router right now.

currently the ethernet cable is connected from data port in office lan network to the board. it was working normal till i did the memtool operation after that it is taking auto ip after software reboot.

I will check with power cycle off and on tomorrow 19th and let u know, if it helps. 

meantime do you have any suggestion for me.

Thank you,

Sreedhar

[weidong_sun]

OK, understood.

    your board is connected to the internal LAN of your company, so server will assign IP address to the board, which is the same result as router.

    For the reason that the IP address is automatically assgined by server, so every time you reboot system , the IP address will be definitely changed.

   So if you hope the board IP not to be changed, you should use "systemd" to set static IP for your board.

  You can search some materials from internet on how to use systemd to set static IP.

   If you didn't find related operations from internel, you can re-create a ticket for the question on community.

Have a nice day!

B.R,

Weidong

[sreedhar_appala]

Thank you weidong,

I will try as suggested.

Regards,

Sreedhar

[sreedhar_appala]

Hi Weidong,

Actually the EVK board did not had a power cycle for a long time and may be its a internal network issue.

I just did power off and power on and it got proper DHCP ip.

Thank you, Sreedhar