RE: PICO-PI-IMX7 and Siging In/Um?


#130

Sir,

Seth here. I shutdown my system, the PICO board, w/ sudo poweroff yesterday. I tried to sign in today via ssh debian@192.168.x.xx.

No route to host <---- This is the error I keep getting. One thing I did notice when “powering” off the board, the LEDs did not turn off.

Seth

P.S. The LEDs on the USB-C connector stayed on.


#131

Sir,

Do not worry about it. I am starting from scratch again.

Seth


#132

Maybe the IP address changed on your dhcp server? Login into your firewall/server/router/etc and find out… There are other ways of achieving access to the pico other then “rebuilding” the eMMC on every failure.

Regards,


#133

Yes Sir,

This is noted now. I erased everything and I started from scratch. I am building the kernel now. For now on, I will check other methods instead of rebuilding.

Seth

P.S. I may have gotten the jumper pins in an inconsistent manner during the first couple of trials. I think this was due to me listening to the manual from TechNexion. Anyway, I think I am on the right track now. If you want, I will update you once more once things are completed.


#134

Hello,

Sir! I am in “emergency mode” right now in the u-boot console. Things booted but in emergency mode. What does this mean? It says and I quote:

You are in emergency mode. After Give root password for maintenance (or press Control-D to continue):

That is what the u-boot console is stating to me right now.

Okay…this is what I did. I typed the root password. Now, I am in a read only file system. This is not good. Do you have any ideas?

What shall I do?

Seth

P.S. Here is the list of ideas I was thinking of researching from the print out on the u-boot console:

U-Boot SPL 2019.01-rc3 (Jan 16 2019 - 20:01:54 -0600)
Trying to boot from MMC1


U-Boot 2019.01-rc3 (Jan 16 2019 - 20:01:54 -0600)

CPU:   Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 42C
Reset cause: POR
Board: i.MX7D PICOSOM
I2C:   ready
DRAM:  512 MiB
PMIC:  PFUZE3000 DEV_ID=0x30 REV_ID=0x11
MMC:   FSL_SDHC: 0
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   FEC0
Hit any key to stop autoboot:  0 
Saving Environment to MMC... Writing to MMC(0)... OK
** No partition table - mmc 0 **
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
209 bytes read in 105 ms (1000 Bytes/s)
1:	Linux 4.20.2-armv7-lpae-x3.zImage
Retrieving file: /boot/vmlinuz-4.20.2-armv7-lpae-x3.zImage
9843200 bytes read in 326 ms (28.8 MiB/s)
append: root=/dev/mmcblk2p1 ro rootfstype=ext4 rootwait quiet
Retrieving file: /boot/dtbs/4.20.2-armv7-lpae-x3.zImage/imx7d-pico-pi.dtb
41336 bytes read in 169 ms (238.3 KiB/s)
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 83000000, end 8300d177

Starting kernel ...

[    0.693375] CPUidle arm: CPU 0 failed to init idle CPU ops
[FAILED] Failed to start File System Check on Root Device.
See 'systemctl status systemd-fsck-root.service' for details.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Reached target Timers.
[  OK  ] Closed Syslog Socket.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Emergency Shell.
[  OK  ] Reached target Emergency Mode.
[  OK  ] Reached target Sockets.
[  OK  ] Started File System Check Daemon to report status.
         Starting Apply Kernel Variables...
         Mounting FUSE Control File System...
         Mounting Configuration File System...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted Configuration File System.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Reached target Local File Systems (Pre).
         Starting udev Coldplug all Devices...
         Starting Load/Save Random Seed...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Reached target Local File Systems.
         Starting Raise network interfaces...
[    2.407885] EXT4-fs error (device mmcblk2p1): ext4_validate_inode_bitmap:100: comm systemd-random-: Corrupt inode bitmap - block_group = 0, inode_bitmap = 473
[  OK  ] Started udev Kernel Device Manager.
[    2.476097] Aborting journal on device mmcblk2p1-8.
[    2.503929] EXT4-fs (mmcblk2p1): Remounting filesystem read-only
[    2.517332] EXT4-fs error (device mmcblk2p1): ext4_journal_check_start:61: Detected aborted journal
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
         Starting Update UTMP about System Boot/Shutdown...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Reached target System Time Synchronized.
[FAILED] Failed to start Update UTMP about System Boot/Shutdown.
See 'systemctl status systemd-update-utmp.service' for details.
[DEPEND] Dependency failed for Update UTMP about System Runlevel Changes.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Started Raise network interfaces.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Found device /dev/ttymxc4.
You are in emergency mode. After Give root password for maintenance
(or press Control-D to continue):

#135

Hello Sir,

The fsck cmd needs to be run manually. I can go into emergency mode and then out of it w/out problems. There is a lot I need to fix.

systemctl status systemd-fsck-root.service is a cmd I ran. It shows that the status is at a failed state.

Seth

P.S. This is what I did so far:

root@arm:~# fsck
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
rootfs contains a file system with errors, check forced.
Resize inode not valid.  Recreate<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  +(0--461) +470 +(473--477) +486 +(489--3008) +(7041--7544) +(8553--8558) +(425984--442367)
Fix<y>? yes
Free blocks count wrong for group #0 (24208, counted=24209).
Fix<y>? yes
Free blocks count wrong (752619, counted=752620).
Fix<y>? yes
Inode bitmap differences:  +(1--11)
Fix<y>? yes

rootfs: ***** FILE SYSTEM WAS MODIFIED *****
rootfs: ***** REBOOT SYSTEM *****
rootfs: 25353/233856 files (0.0% non-contiguous), 181012/933632 blocks
root@arm:~# sudo reboot
[ 2002.382572] EXT4-fs error (device mmcblk2p1): ext4_remount:5239: Abort forced by user
[ 2002.392489] EXT4-fs error (device mmcblk2p1): ext4_remount:5239: Abort forced by user
[ 2002.428280] reboot: Restarting system

#136

@silver2row, correct, running fsck on the trashed file system should be able to “fix” the issue as long as the damage was not to great…

fsck.ext4 -fv /dev/mmcblk2p1

For the “PICO-PI-IMX7”, the most common reason for this happening due to the design of the on-board storage, is simply “yanking” the power supply when the board is running. NEVER do this with ext4, or really any modern File System, that is mounted “rw”…

Your other option is to simply re-install, as you’ve already trashed the file system at this point.

Regards,


#137

Sir,

My number one issue w/ this board so far is this idea. I have not figured out how to remove power w/out pulling the plug out (USB connector) from the computer. The LEDs signify to me that it is on continuously b/c they never go off.

Seth

P.S. I will attempt to make the board work again and again. I will reinstall as usual.


#138

Sir,

I was going to change a couple of things to make this idea work. My host key changed, at least this is what my sign in attempts to tell me via terminal.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:dPs87eBtzVHOb77RhmRRyLExwqFrkNV3PLM75AUVyZE.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:2
remove with:
ssh-keygen -f “/root/.ssh/known_hosts” -R “192.168.x.xx”
ECDSA host key for 192.168.x.xx has changed and you have requested strict checking.
Host key verification failed.


#139

Hello Sir,

Alright, the board is booted, working, and I am upgrading right now. If something happens, I will contact you again for your insight and expertise.

Seth

P.S. I appreciate the steps you took to help me thus far. @RobertCNelson: Sir, do you own this board or have access to this specific board? I am asking b/c the board has no power button. It has a reset button only. I contacted the people that made the board. I will leave it running until the company replies.


#140

@silver2row, why are you calling ssh thru sudo or as root? That’s really not a good practice…

But yeah, your “key” on the PICO changed, as you recreated the image, this is ssh just letting you know something changed…

Regards,


#141

I do have the board and you are correct, there is no power button, it’s best to call “sudo systemctl poweroff” thru the serial terminal when in linux.

Regards,


#142

Sir,

I have this set up of Ubuntu that requires me to do so. I have to use sudo to ssh into my boards.

Seth

P.S. Got you sir. I will use sudo systemctl poweroff next time. Thank you for the info.


#143

Oh and Sir,

Something I found…the instructions from the mfg. are off in the way they call the jumper pins to be aligned. I am glad you came along.

Seth


#144

Sir,

sudo systemctl poweroff works but the LEDs remain on.

Seth

P.S. The board is still around and booted I bet. Anyway…I used that command, sudo systemctl poweroff, in the desktop environment. I will open the desktop up and start the board soon.


#145

Sir,

As much as I can figure, the board only works when it is plugged in before applying power to the desktop. I can plug in the board after my desktop has started and it does not respond.

Seth

P.S. Anyway…that you for the pursuit. I wanted to get this board up and running. Now, I know how to do a bunch of things like Cross Compiling, taking boards away from the Desktop while and after compiling via commands, and porting Linux to a PICO board.


#146

@RobertCNelson:

Sir,

I think this may be an issue w/ the board, the PICO-PI-IMX7, and I wanted to try to update you on this situation.

  1. I cannot sign in on the board unless Ethernet is plugged in.

  1. How do you think I should go about getting WiFi on the board? I just ordered a 2.4GHz antenna for the board.

I was thinking I could just use connmanctl to sign into the WiFi connection via my router credentials.

I tried. But like I typed earlier, the board will not work for some reason unless Ethernet is plugged in.

Seth

P.S. Please send guidance if you ever have some extra time. I sure could use a couple quotes on ideas.


#147

I don’t have that issue…

Debian GNU/Linux 9 arm ttymxc4

default username:password is [debian:temppwd]

arm login: debian
Password: 
Last login: Fri Jan 11 18:42:38 UTC 2019 on ttymxc4

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
debian@arm:~$
debian@arm:~$ uname -r ; cat /proc/device-tree/model
4.20.1-armv7-lpae-x2.1
Technexion Pico i.MX7D Board

First step is to add the ‘correct’ firmware for WiFI, as the mainline one doesn’t work… It would be best to steal from the Pico’s default image…

debian@arm:~$ dmesg | grep firmware
[    0.590825] imx-sdma 30bd0000.sdma: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.590880] imx-sdma 30bd0000.sdma: external firmware not found, using ROM firmware
[   12.642807] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   14.975460] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4339-sdio.txt failed with error 

Regards,


#148

Hello Sir,

Seth here. Here is the command: uname -r ; cat /proc/device-tree/model

4.20.2-armv7-lpae-x3
Technexion Pico i.MX7D Board

Here is dmesg | grep firmware

[    0.590677] imx-sdma 30bd0000.sdma: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.590695] imx-sdma 30bd0000.sdma: external firmware not found, using ROM firmware

Sir,

The PICO default image WiFi setup never worked and it came w/ Android Things and not Debian.

Do you have any ideas?

Seth

P.S. If I need to set up the system from scratch, I can and I will. I will look for the “updated” firmware for the WiFi chip soon. Thank you in advance for any ideas on this matter.


#149

Hello Sir,

I am going off this info: https://www.technexion.com/support/knowledgebase/technexion-bsp-guide-for-kernel-4-1-15/. Supposedly, this is how to set up WiFi on the board.

Anyway…

I just found some files, supposedly the dep. files, and put them in the directory where modprobe can find them. Nothing so far. Do you have any ideas?

Seth

P.S. If there is a source I can review that may be helpful for me, please direct me to that page online.