Posts by JonnyE

JonnyE · Apr 8th 2014

Dear F&S,

what to we have to do to disconnect the CAN transceiver of an armStoneA5 Starter kit?
Do we have to desolder the transceiver or are there any resistance bridges we have to remove?
Simply put, what is the best way to accomplish this?
We want to use our own base board carrying galvanically isolated CAN transceivers.

JonnyE · Feb 11th 2014

Hallo,

we purchased the armStoneA5 starter kit. Using buildroot I created a new root filesystem.
In the config menu I chose remount root filesystem read-write during boot

At the end of the boot process the system tries to generate ssh dsa and rsa keys which delays booting up to nearly 1 minute.

Code

Starting network...
Generating DSA Key...
THIS CAN TAKE A MINUTE OR TWO DEPENDING ON YOUR PROCESSOR!
Generating public/private dsa key pair.
open /etc/ssh_host_dsa_key failed: Read-only file system.
Saving the key failed: /etc/ssh_host_dsa_key.
Generating ECDSA Key...
THIS CAN TAKE A MINUTE OR TWO DEPENDING ON YOUR PROCESSOR!
Generating public/private ecdsa key pair.
open /etc/ssh_host_ecdsa_key failed: Read-only file system.
Saving the key failed: /etc/ssh_host_ecdsa_key.
Starting sshd: Could not load host key: /etc/ssh_host_rsa_key
Could not load host key: /etc/ssh_host_dsa_key
Could not load host key: /etc/ssh_host_ecdsa_key
Disabling protocol version 2. Could not load host key
sshd: no hostkeys available -- exiting.
OK
Starting input-event-daemon: done
Welcome to F+S-Vybrid
fsvybrid login:

Display More

We tried to remount the filesystem rw and generate these keys manually using

Code

fsvybrid login: root
# mount -o remount,rw /
UBIFS: completing deferred recovery
UBIFS: deferred recovery completed
# ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/root/.ssh/id_dsa): /etc/ssh_host_dsa_key
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /etc/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh_host_dsa_key.pub.
The key fingerprint is:
c1:c5:99:ea:dc:1f:bf:9f:52:1b:44:07:04:8f:4c:19 root@fsvybrid
The key's randomart image is:
+--[ DSA 1024]----+
| ..oE=o. |
| . .+o.o ..|
| o. o o .|
| .. . |
| oS. . |
| o . . o |
| . o. o|
| .....|
| o+.|
+-----------------+
# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): /etc/ssh_host_rsa_key
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /etc/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh_host_rsa_key.pub.
The key fingerprint is:
b1:b1:4f:25:80:df:5b:37:e2:c9:1f:69:00:54:bb:2d root@fsvybrid
The key's randomart image is:
+--[ RSA 2048]----+
| ...... |
| . .. . |
| .o...o |
| .=.o+oo |
| S .=E=.o |
| o. +.+ |
| . o . |
| . |
| |
+-----------------+
# ssh-keygen -t ecdsa
Generating public/private ecdsa key pair.
Enter file in which to save the key (/root/.ssh/id_ecdsa): /etc/ssh_host_ecdsa_key
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /etc/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh_host_ecdsa_key.pub.
The key fingerprint is:
6c:23:e7:eb:fd:3b:96:91:e2:32:32:a3:83:c7:71:e0 root@fsvybrid
The key's randomart image is:
+--[ECDSA 256]---+
| |
| |
| |
| . . |
| . .. S . |
| E .= .. o |
| o o .. . o |
| . + + oo. + |
| ..o =oo.ooo |
+-----------------+
#

Display More

But we didn't have success. I've also tried restoring the root filesystem using rootfs_std-fsvybrid-V1.0.ubifs from the fsvybrid-V1.0.tar.bz2 archive.
What do I have to do to generate these keys and save them permanently in order to make the boot up delay disappear?
Why is my root filesystem not mounted rw although I've chosen it in buildroot?

Thank you very much!

JonnyE · Feb 11th 2014

Hallo,

thank you very much.

1. load the root filesystem image via tftp
2. ubi part TargetFS
3. ubi write $loadaddr rootfs $filesize

I was able to write the root filesystem

JonnyE · Feb 10th 2014

Hello,
I just want to replace the existing root filesystem with the one I've created from buildroot. As you pointed that
a user volume already exists, I tried to download and write immediately, but without success.

Code

armStoneA5 # ubi write $loadaddr rootfs $filesize
Error, no UBI device/partition selected!

So I tried to find out how the existing partition is named and
unsuccessfully used the ubi info layout command you mentioned.

Code

armStoneA5 # ubi info layout
Error, no UBI device/partition selected!

I was looking for some help and found the following documentation:
http://www.linux-mtd.infradead.org/doc/ubi.html#L_usptools
They use a slightly other syntax, commands are without spaces, and the mentioned -h option does not work
when I'm operating on armStoneA5.
Can you provide a documentation for the ubi tools you use on armStoneA5 or
give me the sequence of commands I have to use for replacing the root filesystem?
What did I do wrong with the ubi info layout command?

JonnyE · Feb 7th 2014

Dear F&S,

we purchased the armstone A5 Starter Kit. I've created a rootfs image using buildroot and tried to load it following the guide Vibrid Linux First Steps starting at section 4.4 Load and Save Root File System. Unfortunately
command ubi create rootfs fails. What did I miss? Here is my log:

Code

armStoneA5 # tftp rootfs.ubifs
Using FEC1 device
TFTP from server 192.168.101.42; our IP address is 192.168.101.30
Filename 'rootfs.ubifs'.
Load address: 0x80800000
Loading: TX timeout
TX timeout
TX not ready
TX timeout
TX not ready
TX timeout
ARP Retry count exceeded; starting again
Using FEC0 device
TFTP from server 192.168.101.42; our IP address is 192.168.101.30
Filename 'rootfs.ubifs'.
Load address: 0x80800000
Loading: #####################...###########
done
Bytes transferred = 30062592 (0x1cab800)
armStoneA5 # ubi part TargetFS
Creating 1 MTD partitions on "nand0":
0x000000800000-0x000008000000 : "mtd=6"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=6"
UBI: MTD device size: 120 MiB
UBI: number of good PEBs: 960
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 960
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 4/1
armStoneA5 # ubi create rootfs
No size specified -> Using max size (0)
No space left in UBI device!
verify_mkvol_req failed 12

Display More

Posts by JonnyE

Disconnecting CAN tranceiver of armStoneA5 starter kit

ssh key generation delays booting

Error loading root filesystem

Error loading root filesystem

Error loading root filesystem