Quote:
|
Do you remote in over u-boot or linux ?
|
I use Tera Term on Windows 10, connecting to a COM port associated with an FTDI adapter. I can connect to u-boot (if I hit a key during the startup sequence) or to a bash shell once it boots to the file system.
Here's the output for those commands.
Code:
# pkill nickel
# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "uboot"
mtd1: 001e0000 00020000 "kernel"
mtd2: 000c0000 00020000 "picture"
mtd3: 00020000 00020000 "parameters"
mtd4: 0a000000 00020000 "rootfs"
mtd5: 00100000 00020000 "app"
mtd6: 35b40000 00020000 "other"
# cat /proc/partitions
major minor #blocks name
31 0 512 mtdblock0
31 1 1920 mtdblock1
31 2 768 mtdblock2
31 3 128 mtdblock3
31 4 163840 mtdblock4
31 5 1024 mtdblock5
31 6 879872 mtdblock6
# find /dev -iname mtdblock*
/dev/mtdblock5
/dev/mtdblock2
/dev/mtdblock3
/dev/mtdblock4
/dev/mtdblock6
/dev/mtdblock0
/dev/mtdblock1
# udevd --daemon
/bin/sh: udevd: not found
# udevadm
/bin/sh: udevadm: not found
# dd if=/dev/zero of=/dev/mtdblock6 bs=1M conv=fsync
**>> Block 534 retired
Block 534 is in state 9 after gc, should be erased
dd: can't open '/dev/mtdblock6': No such device or address
# dd if=/dev/zero of=/dev/mtdblock6 bs=512 conv=fsync
dd: can't open '/dev/mtdblock6': No such device or address