DSignT Support Database - User contributions [en]

File:Copy RootFS to NFS.jpg

2017-11-17T11:43:34Z

Claus: Claus uploaded a new version of File:Copy RootFS to NFS.jpg

Booting Linux from QSPI on AMC1 with RFS on eMMC

2017-11-17T11:43:08Z

Claus:

== Preparation ==
Follow steps 1-4 of [[Booting Linux from QSPI on AMC1 with RFS on NFS]] and boot into Linux on the AMC1

<syntaxhighlight lang=text style="border:1px dashed blue">
Kernel image @ 0x80200000 [ 0x000000 - 0x395e58 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 8800d630

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.41-ge3a80a1c5c (sitara@sitara-sdk401) (gcc vers
ion 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Wed Oct 25 14:53:44 CEST 20
17
...
[ 9.670506] systemd[1]: Detected architecture arm.

Welcome to Arago 2017.06!

[ 9.722230] systemd[1]: Set hostname to <am437x-evm>.
...
_____ _____ _ _
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
|___| |___|

Arago Project http://arago-project.org am437x-evm ttyO0

Arago 2017.06 am437x-evm ttyO0

am437x-evm login: root
root@am437x-evm:~#
</syntaxhighlight>

 

== Prepare eMMC ==
=== Check if eMMC is available ===
'''''ls -lah /dev/ | grep mmc'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# ls -lah /dev/ | grep mmc
brw-rw---- 1 root disk 179, 0 Sep 26 21:32 mmcblk0
brw-rw---- 1 root disk 179, 16 Sep 26 21:32 mmcblk0boot0
brw-rw---- 1 root disk 179, 32 Sep 26 21:33 mmcblk0boot1
brw-rw---- 1 root disk 179, 1 Sep 26 21:33 mmcblk0p1
root@am437x-evm:~#
</syntaxhighlight>

'''''mmcblk0''''' is the on-board eMMC
 
=== Start '''''fdisk''''' ===
'''''fdisk /dev/mmcblk0'''''
<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# fdisk /dev/mmcblk0

Welcome to fdisk (util-linux 2.28.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help):
</syntaxhighlight>
 
=== Clear existing partition ===
Command '''''o''''' clears any existing partition on device mmcblk0 and creates a new disklable

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): o
Created a new DOS disklabel with disk identifier 0xc4fcd91f.

Command (m for help):
</syntaxhighlight>
 
=== List all partiotions ===
Command '''''p''''' will list all partition tables on eMMC

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): p
Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc4fcd91f

Command (m for help):
</syntaxhighlight>
 
=== Create new partition ===
Create a new partition with command '''''n'''''.

Enter '''''p''''' for a primary partition, Partition number is 1, first sector is 2048 and +64M is the boot partition size.
{{note|We initially create a boot partition even if it is not used due to QSPI boot. This makes it possible to copy MLO + U-Boot + Linux Kernel later without destroying a potentially existing Root FS on a different partition. }}
 
<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-15269887, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-15269887, default 15269887): +64M

Created a new partition 1 of type 'Linux' and of size 64 MiB.

Command (m for help):
</syntaxhighlight>
 
If this partition should be used later for booting - remember we do not need it since QSPI boot is default - make this partition bootable. For this the partition type must be set to '''''W95 FAT16 (LBA)''''':

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): t
Selected partition 1
Partition type (type L to list all types): e
Changed type of partition 'Linux' to 'W95 FAT16 (LBA)'.

Command (m for help):
</syntaxhighlight>

and the '''''boot''''' flag must be set by command '''''a''''':
<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): a
Selected partition 1
The bootable flag on partition 1 is enabled now.

Command (m for help):
</syntaxhighlight>

Check success:
<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): p
Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc4fcd91f

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 133119 131072 64M e W95 FAT16 (LBA)

Command (m for help):
</syntaxhighlight>
 
{{pagetop}}
=== Create second partition ===
Create a second partition for the Root FS. Enter command '''''n''''' to create a new partition. Partition type is '''''p''''' for primary. Partition numer is '''''2''''', first and last sector set to default.

<syntaxhighlight lang=text style="border:1px dashed blue">
command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2): 2
First sector (133120-15269887, default 133120):
Last sector, +sectors or +size{K,M,G,T,P} (133120-15269887, default 15269887):

Created a new partition 2 of type 'Linux' and of size 7.2 GiB.

Command (m for help): p
Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc4fcd91f

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 133119 131072 64M e W95 FAT16 (LBA)
/dev/mmcblk0p2 133120 15269887 15136768 7.2G 83 Linux

Command (m for help):
</syntaxhighlight>

 
=== Write partition table to eMMC ===
Command '''''w''''' writes the new partition table back to eMMC:

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
[ 3589.507368] mmcblk0: p1 p2
Syncing disks.

root@am437x-evm:~#
</syntaxhighlight>
 

=== Format partitions ===
Format boot partition with FAT:
'''''mkfs.vfat -F 16 /dev/mmcblk0p1'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# mkfs.vfat -F 16 /dev/mmcblk0p1
mkfs.fat 4.0 (2016-05-06)
root@am437x-evm:~#
</syntaxhighlight>
 
Format Root FS partition with EXT4:
'''''mkfs.ext4 /dev/mmcblk0p2'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# mkfs.ext4 /dev/mmcblk0p2
mke2fs 1.43 (17-May-2016)
Discarding device blocks: done
Creating filesystem with 1892096 4k blocks and 473280 inodes
Filesystem UUID: 09e4e558-553e-455d-b93f-542ed41a1f4f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

root@am437x-evm:~#
</syntaxhighlight>

 
== Copy Root FS tarball ==
Copy a Root FS tarball to a directory on your NFS server:

[[File:Copy_RootFS_to_NFS.jpg]]
 
== Extract Root FS to eMMC ==
Extract the Root FS to the eMMC with the following commands:

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# cd /tmp
root@am437x-evm:/tmp# mkdir rootfs
root@am437x-evm:/tmp# mount /dev/mmcblk0p2 rootfs
root@am437x-evm:/tmp# tar -xJf /home/arago-base-tisdk-image-am437x-evm.tar.xz -C rootfs
root@am437x-evm:/tmp# umount /dev/mmcblk0p2
</syntaxhighlight>

This step may take a few minutes depending on the size of your Root FS.
 

== Reboot and change bootparam ==
Reboot the system using '''''reboot''''' command. Enter the U-Boot command processor and change the bootparam:

'''''setenv bootargs root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
AMC1> setenv bootargs root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
</syntaxhighlight>

 
== start Linux with Root FS on eMMC ==
'''''setenv loadimage 'sf read ${loadaddr} 0x200000 0x400000' '''''
'''''setenv loaddtb 'sf read ${fdtaddr} 0x120000 0x10000' '''''
'''''sf probe && run loadimage loaddtb && bootz ${loadaddr} - ${fdtaddr}'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
AMC1> setenv loadimage 'sf read ${loadaddr} 0x200000 0x400000'
AMC1> setenv loaddtb 'sf read ${fdtaddr} 0x120000 0x10000'
AMC1> sf probe && run loadimage loaddtb && bootz ${loadaddr} - ${fdtaddr}
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
device 0 offset 0x200000, size 0x400000
SF: 4194304 bytes @ 0x200000 Read: OK
device 0 offset 0x120000, size 0x10000
SF: 65536 bytes @ 0x120000 Read: OK
Kernel image @ 0x80200000 [ 0x000000 - 0x395e58 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 8800d630

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.41-ge3a80a1c5c (sitara@sitara-sdk401) (gcc vers
ion 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Wed Oct 25 14:53:44 CEST 20
17
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
...
[ 2.346390] systemd[1]: Detected architecture 'arm'.

Welcome to Arago 2017.06!

...
***************************************************************
_____ _____ _ _
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
|___| |___|

Arago Project http://arago-project.org am437x-evm ttyO0

Arago 2017.06 am437x-evm ttyO0

am437x-evm login:
</syntaxhighlight>

 

== Additional Tags ==
[[Booting Linux from QSPI on AMC1 with RFS on NFS]]
[[Network settings for U-Boot on AMC1]]

[[category:AMC1]]

File:Copy RootFS to NFS.jpg

2017-11-16T16:00:51Z

Claus:

Booting Linux from QSPI on AMC1 with RFS on eMMC

2017-11-16T16:00:20Z

Claus: Created page with "== Preparation == Follow steps 1-4 of Booting Linux from QSPI on AMC1 with RFS on NFS and boot into Linux on the AMC1 <syntaxhighlight lang=text style="border:1px dashed..."

== Preparation ==
Follow steps 1-4 of [[Booting Linux from QSPI on AMC1 with RFS on NFS]] and boot into Linux on the AMC1

<syntaxhighlight lang=text style="border:1px dashed blue">
Kernel image @ 0x80200000 [ 0x000000 - 0x395e58 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 8800d630

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.41-ge3a80a1c5c (sitara@sitara-sdk401) (gcc vers
ion 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Wed Oct 25 14:53:44 CEST 20
17
...
[ 9.670506] systemd[1]: Detected architecture arm.

Welcome to Arago 2017.06!

[ 9.722230] systemd[1]: Set hostname to <am437x-evm>.
...
_____ _____ _ _
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
|___| |___|

Arago Project http://arago-project.org am437x-evm ttyO0

Arago 2017.06 am437x-evm ttyO0

am437x-evm login: root
root@am437x-evm:~#
</syntaxhighlight>

 

== Prepare eMMC ==
=== Check if eMMC is available ===
'''''ls -lah /dev/ | grep mmc'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# ls -lah /dev/ | grep mmc
brw-rw---- 1 root disk 179, 0 Sep 26 21:32 mmcblk0
brw-rw---- 1 root disk 179, 16 Sep 26 21:32 mmcblk0boot0
brw-rw---- 1 root disk 179, 32 Sep 26 21:33 mmcblk0boot1
brw-rw---- 1 root disk 179, 1 Sep 26 21:33 mmcblk0p1
root@am437x-evm:~#
</syntaxhighlight>

'''''mmcblk0''''' is the on-board eMMC
 
=== Start '''''fdisk''''' ===
'''''fdisk /dev/mmcblk0'''''
<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# fdisk /dev/mmcblk0

Welcome to fdisk (util-linux 2.28.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help):
</syntaxhighlight>
 
=== Clear existing partition ===
Command '''''o''''' clears any existing partition on device mmcblk0 and creates a new disklable

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): o
Created a new DOS disklabel with disk identifier 0xc4fcd91f.

Command (m for help):
</syntaxhighlight>
 
=== List all partiotions ===
Command '''''p''''' will list all partition tables on eMMC

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): p
Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc4fcd91f

Command (m for help):
</syntaxhighlight>
 
=== Create new partition ===
Create a new partition with command '''''n'''''.

Enter '''''p''''' for a primary partition, Partition number is 1, first sector is 2048 and +64M is the boot partition size.
{{note|We initially create a boot partition even if it is not used due to QSPI boot. This makes it possible to copy MLO + U-Boot + Linux Kernel later without destroying a potentially existing Root FS on a different partition. }}
 
<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-15269887, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-15269887, default 15269887): +64M

Created a new partition 1 of type 'Linux' and of size 64 MiB.

Command (m for help):
</syntaxhighlight>
 
If this partition should be used later for booting - remember we do not need it since QSPI boot is default - make this partition bootable. For this the partition type must be set to '''''W95 FAT16 (LBA)''''':

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): t
Selected partition 1
Partition type (type L to list all types): e
Changed type of partition 'Linux' to 'W95 FAT16 (LBA)'.

Command (m for help):
</syntaxhighlight>

and the '''''boot''''' flag must be set by command '''''a''''':
<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): a
Selected partition 1
The bootable flag on partition 1 is enabled now.

Command (m for help):
</syntaxhighlight>

Check success:
<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): p
Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc4fcd91f

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 133119 131072 64M e W95 FAT16 (LBA)

Command (m for help):
</syntaxhighlight>
 
{{pagetop}}
=== Create second partition ===
Create a second partition for the Root FS. Enter command '''''n''''' to create a new partition. Partition type is '''''p''''' for primary. Partition numer is '''''2''''', first and last sector set to default.

<syntaxhighlight lang=text style="border:1px dashed blue">
command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2): 2
First sector (133120-15269887, default 133120):
Last sector, +sectors or +size{K,M,G,T,P} (133120-15269887, default 15269887):

Created a new partition 2 of type 'Linux' and of size 7.2 GiB.

Command (m for help): p
Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc4fcd91f

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 133119 131072 64M e W95 FAT16 (LBA)
/dev/mmcblk0p2 133120 15269887 15136768 7.2G 83 Linux

Command (m for help):
</syntaxhighlight>

 
=== Write partition table to eMMC ===
Command '''''w''''' writes the new partition table back to eMMC:

<syntaxhighlight lang=text style="border:1px dashed blue">
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
[ 3589.507368] mmcblk0: p1 p2
Syncing disks.

root@am437x-evm:~#
</syntaxhighlight>
 

=== Format partitions ===
Format boot partition with FAT:
'''''mkfs.vfat -F 16 /dev/mmcblk0p1'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# mkfs.vfat -F 16 /dev/mmcblk0p1
mkfs.fat 4.0 (2016-05-06)
root@am437x-evm:~#
</syntaxhighlight>
 
Format Root FS partition with EXT4:
'''''mkfs.ext4 /dev/mmcblk0p2'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# mkfs.ext4 /dev/mmcblk0p2
mke2fs 1.43 (17-May-2016)
Discarding device blocks: done
Creating filesystem with 1892096 4k blocks and 473280 inodes
Filesystem UUID: 09e4e558-553e-455d-b93f-542ed41a1f4f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

root@am437x-evm:~#
</syntaxhighlight>

 
== Copy Root FS tarball ==
Copy a Root FS tarball to a directory on your NFS server:

[[File:Copy_RootFS_to_NFS.jpg]]
 
== Extract Root FS to eMMC ==
Extract the Root FS to the eMMC with the following commands:

<syntaxhighlight lang=text style="border:1px dashed blue">
root@am437x-evm:~# cd /tmp
root@am437x-evm:/tmp# mkdir rootfs
root@am437x-evm:/tmp# mount /dev/mmcblk0p2 rootfs
root@am437x-evm:/tmp# tar -jxvf /home/debian-image.tar.bz2 rootfs
root@am437x-evm:/tmp# umount /dev/mmcblk0p2
</syntaxhighlight>

This step may take a few minutes depending on the size of your Root FS.
 
== Reboot and change bootparam ==
Reboot the system using '''''reboot''''' command. Enter the U-Boot command processor and change the bootparam:

'''''setenv bootargs root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
AMC1> setenv bootargs root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
</syntaxhighlight>

 
== start Linux with Root FS on eMMC ==
'''''setenv loadimage 'sf read ${loadaddr} 0x200000 0x400000' '''''
'''''setenv loaddtb 'sf read ${fdtaddr} 0x120000 0x10000' '''''
'''''sf probe && run loadimage loaddtb && bootz ${loadaddr} - ${fdtaddr}'''''

<syntaxhighlight lang=text style="border:1px dashed blue">
AMC1> setenv loadimage 'sf read ${loadaddr} 0x200000 0x400000'
AMC1> setenv loaddtb 'sf read ${fdtaddr} 0x120000 0x10000'
AMC1> sf probe && run loadimage loaddtb && bootz ${loadaddr} - ${fdtaddr}
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
device 0 offset 0x200000, size 0x400000
SF: 4194304 bytes @ 0x200000 Read: OK
device 0 offset 0x120000, size 0x10000
SF: 65536 bytes @ 0x120000 Read: OK
Kernel image @ 0x80200000 [ 0x000000 - 0x395e58 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 8800d630

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.41-ge3a80a1c5c (sitara@sitara-sdk401) (gcc vers
ion 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Wed Oct 25 14:53:44 CEST 20
17
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
...
[ 2.346390] systemd[1]: Detected architecture 'arm'.

Welcome to Debian GNU/Linux 8 (jessie)!
...
[ OK ] Started Serial Getty on ttyO0.
[ OK ] Reached target Login Prompts.

Debian GNU/Linux 8 cm-debian ttyO0

cm-debian login:
</syntaxhighlight>

 

== Additional Tags ==
[[Booting Linux from QSPI on AMC1 with RFS on NFS]]
[[Network settings for U-Boot on AMC1]]

[[category:AMC1]]

Booting Linux from QSPI on AMC1 with RFS on NFS

2017-11-16T12:52:10Z

Claus: Created page with "__NOINDEX__ == Preparation == Boot into U-Boot and stop execution by pressing a key <syntaxhighlight lang=c style="border:1px dashed blue"> U-Boot 2017.01 (Nov 14 2017 - 13..."

__NOINDEX__

== Preparation ==
Boot into U-Boot and stop execution by pressing a key

<syntaxhighlight lang=c style="border:1px dashed blue">
U-Boot 2017.01 (Nov 14 2017 - 13:37:55 +0100)

CPU : AM437X-GP rev 1.2
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
In: serial
Out: serial
Err: serial
Net: cpsw
Hit any key to stop autoboot: 0
AMC1>
</syntaxhighlight>
 

To boot a Linux Kernel from QSPI Flash you first need to load a Kernel and a DTB from either [[#Use TFTP server|TFTP server]] or from [[#Use USB Stick|USB stick]] and store these images on the QSPI Flash at suitable address offsets. Ref. to [[Serial FLASH mapping on AMC1]].

 

== Load Kernel Image and DTB ==
=== Use TFTP server ===
==== Network settings ====
To access the TFTP server you need to do a proper network configuration first. Either enter all necessary environment variables manually on the U-Boot command prompt or use script [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]] to make all these settings automatically.

Required network settings: 
[[Network_settings_for_U-Boot_on_AMC1#ethaddr.2C_eth1addr|'''''eth1addr''''']] - own MAC address 
AMC1> setenv eth1addr c4:be:84:cb:1f:ff

[[Network_settings_for_U-Boot_on_AMC1#ipaddr|'''''ipaddr''''']] - own IP address 
AMC1> setenv ipaddr 192.168.168.197

[[Network_settings_for_U-Boot_on_AMC1#serverip|'''''serverip''''']] - remote server IP
AMC1> setenv serverip 192.168.168.208

==== Load compressed Linux image from TFTP server ====
If all network settings are correct, a compressed Linux image can be loaded from TFTP server:
'''''tftpboot ${loadaddr} zImage-dsignt_amc1.bin'''''

'''''${loadaddr}''''' is a pre-defined environment variable that specifies a free DDR RAM location for general purpose. We use it here as a temporary storage address for the TFTP transfer.

When the TFTP transfer succeeds, each received block (512 bytes) a '#' is printed on the terminal else a 'T' for timeout signals a problem connecting the server. A successful transmission can look like this (of course the IP addresses vary depending on your network configuration):

<syntaxhighlight lang=c style="border:1px dashed blue">
MC1> tftpboot ${loadaddr} zImage-dsignt_amc1.bin
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.208; our IP address is 192.168.168.194
Filename 'zImage-dsignt_amc1.bin'.
Load address: 0x80200000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
####################
1.3 MiB/s
done
Bytes transferred = 3759704 (395e58 hex)
AMC1>
</syntaxhighlight>

 

==== Load DTB from TFTP server ====
'''''tftpboot ${fdtaddr} amc1.dtb'''''

'''''${fdtaddr}''''' is a pre-defined environment variable that specifies a free DDR RAM location for general purpose. We use it here as a temporary storage address for the TFTP transfer.

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> tftpboot ${fdtaddr} amc1.dtb
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.208; our IP address is 192.168.168.194
Filename 'amc1.dtb'.
Load address: 0x88000000
Loading: #########
1.2 MiB/s
done
Bytes transferred = 42545 (a631 hex)
AMC1>
</syntaxhighlight>
 
Continue with step 3 [[#Write_Image_and_DTB_to_Flash|Write Image and DTB to Flash]]

 

=== Use USB Stick ===
==== '''''usb start''''' and '''''usb info''''' ====
'''''usb start'''''
Initialize the USB controler and enumerate all USB devices
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> usb start
starting USB...
USB0: Register 2000440 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
AMC1>
</syntaxhighlight>
 
'''''usb info'''''
Print detailed information of enumerated devices
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> usb info
1: Hub, USB Revision 3.0
- U-Boot XHCI Host Controller
- Class: Hub
- PacketSize: 9 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage, USB Revision 2.0
- USBest Technology USB Mass Storage Devie 1009135102477e
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x1307 Product 0x0165 Version 1.0
Configuration: 1
- Interfaces: 1 Bus Powered 98mA
Interface: 0
- Alternate Setting 0, Endpoints: 3
- Class Mass Storage, Transp. SCSI, Bulk only
- Endpoint 1 Out Bulk MaxPacket 512
- Endpoint 2 In Bulk MaxPacket 512
- Endpoint 3 In Interrupt MaxPacket 64 Interval 8ms

AMC1>
</syntaxhighlight>
 
==== Load compressed Linux image from USB stick ====
'''''fatload usb 0 ${loadaddr} zimage-dsignt_amc1.bin'''''
Load Kernel image from USB mass storage device into RAM

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> fatload usb 0 ${loadaddr} zimage-dsignt_amc1.bin
reading zimage-dsignt_amc1.bin
3759704 bytes read in 2080 ms (1.7 MiB/s)
AMC1>
</syntaxhighlight>
 

==== Load DTB from USB stick ====
'''''fatload usb 0 ${fdtaddr} amc1.dtb'''''
Load DTB from USB mass storage device into RAM

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> fatload usb 0 ${fdtaddr} amc1.dtb
reading amc1.dtb
41451 bytes read in 44 ms (919.9 KiB/s)
AMC1>
</syntaxhighlight>
 
Continue with step 3 [[#Write_Image_and_DTB_to_Flash|Write Image and DTB to Flash]]

 

== Write Image and DTB to Flash ==
=== '''''sf probe''''' ===
First check if a serial FLASH is available:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
 
=== '''''sf erase''''' ===
If the probe command finds a serial FLASH, use the erase command to clear the U-Boot FLASH area:

DTB:
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf erase 0x120000 0x10000
SF: 65536 bytes @ 0x120000 Erased: OK
AMC1>
</syntaxhighlight>

Linux Kernel (assumed filesize < 0x400000):
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf erase 0x200000 0x400000
SF: 4194304 bytes @ 0x200000 Erased: OK
AMC1>
</syntaxhighlight>

 
=== '''''sf write''''' ===
'''''sf write''''' writes a previously loaded image from RAM to serial FLASH

DTB:
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf write ${fdtaddr} 0x120000 0x10000
device 0 offset 0x120000, size 0x10000
SF: 65536 bytes @ 0x120000 Written: OK
AMC1>
</syntaxhighlight>

Linux Kernel:
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf write ${loadaddr} 0x200000 0x400000
device 0 offset 0x200000, size 0x400000
SF: 4194304 bytes @ 0x200000 Written: OK
AMC1>
</syntaxhighlight>

 

== re-boot and load the image ==
After re-boot you need to probe for the SF first:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
 
=== Load Kernel and DTB from QSPI Flash ===

'''''sf read ${loadaddr} 0x200000 0x400000'''''

'''''sf read ${fdtaddr} 0x120000 0x10000'''''

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf read ${loadaddr} 0x200000 0x400000
device 0 offset 0x200000, size 0x400000
SF: 4194304 bytes @ 0x200000 Read: OK
AMC1> sf read ${fdtaddr} 0x120000 0x10000
device 0 offset 0x120000, size 0x10000
SF: 65536 bytes @ 0x120000 Read: OK
AMC1>
</syntaxhighlight>

 
=== Set bootargs ===
The global environment variable '''''bootargs''''' is automatically passed to the booting Linux. Make sure '''''nfsroot''''' points to the valid NFS path on your NFS server:

'''''setenv bootargs root=/dev/nfs rw rootfstype=ext4 rootwait fixrtc nfsroot=${serverip}:/home/sitara/ti-processor-sdk-linux-am437x-evm-04.01.00.06/targetNFS,vers=3 ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${device}:${autoconf}'''''

In this case with installed SDK 04.01.00.06 tools on server ${serverip} the correct path is:
${serverip}:/home/sitara/ti-processor-sdk-linux-am437x-evm-04.01.00.06/targetNFS

 

=== Boot Linux zImage ===
'''''bootz ${loadaddr} - ${fdtaddr}'''''

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> bootz ${loadaddr} - ${fdtaddr}
Kernel image @ 0x80200000 [ 0x000000 - 0x395e58 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 8800d630

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.41-ge3a80a1c5c (sitara@sitara-sdk401)
...
</syntaxhighlight>

 

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]

[[category:AMC1]]

Backup and restore U-Boot environment on AMC1

2017-11-16T11:24:27Z

Claus:

Save DTB to serial FLASH on AMC1 via U-Boot

2017-11-16T10:10:47Z

Claus:

__NOINDEX__

== Load DTB ==
=== from TFTP server ===
Load a DTB image from TFTP server (correct network settings provided: [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]]):

'''''tftpboot ${fdtaddr} amc1.dtb'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> tftpboot ${fdtaddr} amc1.dtb
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.203
Filename 'amc1.dtb'.
Load address: 0x88000000
Loading: #########
641.6 KiB/s
done
Bytes transferred = 41451 (a1eb hex)
AMC1>
</syntaxhighlight>

=== from USB memory stick ===
==== '''''usb start''''' ====
<syntaxhighlight lang=c style="border:1px blue">
MC1> usb start
starting USB...
USB0: Register 2000440 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
AMC1>
</syntaxhighlight>

==== '''''fatload usb 0:1 ${fdtaddr} amc1.dtb''''' ====
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fatload usb 0:1 ${fdtaddr} amc1.dtb
reading amc1.dtb
41451 bytes read in 44 ms (919.9 KiB/s)
AMC1>
</syntaxhighlight>

=== from serial FLASH ===
If a DTB was previously saved somewhere in serial FLASH (e.g as backup), this image can be loaded
==== '''''sf probe''''' ====
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, mapped at 30000000
AMC1>
</syntaxhighlight>

==== '''''sf read ${fdtaddr} 0x150000 0x10000''''' ====

<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf read ${fdtaddr} 0x150000 0x10000
device 0 offset 0x150000, size 0x10000
SF: 65536 bytes @ 0x150000 Read: OK
AMC1>
</syntaxhighlight>
 

== Verify DTB ==
configure the fdt tool to point to the fdtaddr:
'''''fdt addr ${fdtaddr}'''''

If the DTB image is bad, you should get the error message:
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fdt addr ${fdtaddr}
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
AMC1>
</syntaxhighlight>

In case a valid DTB is found on the address, nothing is printed and you can proceed to list more details.
Enter '''''fdt header''''' command:
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fdt header
magic: 0xd00dfeed
totalsize: 0xa1eb (41451)
off_dt_struct: 0x38
off_dt_strings: 0x9a60
off_mem_rsvmap: 0x28
version: 17
last_comp_version: 16
boot_cpuid_phys: 0x0
size_dt_strings: 0x78b
size_dt_struct: 0x9a28
number mem_rsv: 0x0

AMC1>
</syntaxhighlight>

 
== Save to serial FLASH ==
=== '''''sf probe''''' ===
First step to access the QSPI FLASH is to probe for the SF. If not yet probed, execute probe command
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, mapped at 30000000
AMC1>
</syntaxhighlight>

=== Erase FLASH area ===
'''''sf erase 0x120000 0x10000'''''
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf erase 0x120000 0x10000
SF: 65536 bytes @ 0x120000 Erased: OK
AMC1>
</syntaxhighlight>

=== Write DTB to serial FLASH ===
'''''sf write ${fdtaddr} 0x120000 0x10000'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf write ${fdtaddr} 0x120000 0x10000
device 0 offset 0x120000, size 0x10000
SF: 65536 bytes @ 0x120000 Written: OK
AMC1>
</syntaxhighlight>
 
{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
[[Network settings for U-Boot on AMC1]]
[[Save Linux Kernel to serial FLASH on AMC1 via U-Boot]]

[[category:AMC1]]

Save Linux Kernel to serial FLASH on AMC1 via U-Boot

2017-11-16T10:10:22Z

Claus: Created page with "__NOINDEX__ == Load Linux Kernel == === from TFTP server === Load a Kernel image from TFTP server (correct network settings provided: Network_settings_for_U-Boot_on_AMC1#Sc..."

__NOINDEX__

== Load Linux Kernel ==
=== from TFTP server ===
Load a Kernel image from TFTP server (correct network settings provided: [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]]):

'''''tftpboot ${loadaddr} zImage-dsignt_amc1.bin'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> tftpboot ${loadaddr} zImage-dsignt_amc1.bin
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.208; our IP address is 192.168.168.173
Filename 'zImage-dsignt_amc1.bin'.
Load address: 0x80200000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
####################
1 MiB/s
done
Bytes transferred = 3759704 (395e58 hex)
AMC1>
</syntaxhighlight>

=== from USB memory stick ===
==== '''''usb start''''' ====
<syntaxhighlight lang=c style="border:1px blue">
MC1> usb start
starting USB...
USB0: Register 2000440 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
AMC1>
</syntaxhighlight>

==== '''''fatload usb 0:1 ${loadaddr} zImage-dsignt_amc1.bin''''' ====
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fatload usb 0:1 ${loadaddr} zImage-dsignt_amc1.bin
reading zImage-dsignt_amc1.bin
3759704 bytes read in 2080 ms (1.7 MiB/s)
AMC1>
</syntaxhighlight>

 
== Save to serial FLASH ==
=== '''''sf probe''''' ===
First step to access the QSPI FLASH is to probe for the SF. If not yet probed, execute probe command
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, mapped at 30000000
AMC1>
</syntaxhighlight>

=== Erase FLASH area ===
'''''sf erase 0x200000 0x400000'''''
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf erase 0x200000 0x400000
AMC1>
SF: 4194304 bytes @ 0x200000 Erased: OK
</syntaxhighlight>

=== Write Kernel to serial FLASH ===
'''''sf write ${loadaddr} 0x200000 0x400000'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf write ${loadaddr} 0x200000 0x400000
device 0 offset 0x200000, size 0x400000
SF: 4194304 bytes @ 0x200000 Written: OK
AMC1>
</syntaxhighlight>
 
{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
[[Network settings for U-Boot on AMC1]]
[[Save DTB to serial FLASH on AMC1 via U-Boot]]

[[category:AMC1]]

Save DTB to serial FLASH on AMC1 via U-Boot

2017-11-16T09:46:03Z

Claus:

Update U-Boot Image via USB on AMC1

2017-11-16T09:28:19Z

Claus:

__NOINDEX__

== '''''usb start''''' ==
'''''usb start'''''
Initialize the USB controler and enumerate all USB devices
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> usb start
starting USB...
USB0: Register 2000440 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
AMC1>
</syntaxhighlight>
 
'''''usb info'''''
Print detailed information of enumerated devices
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> usb info
1: Hub, USB Revision 3.0
- U-Boot XHCI Host Controller
- Class: Hub
- PacketSize: 9 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage, USB Revision 2.0
- USBest Technology USB Mass Storage Devie 1009135102477e
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x1307 Product 0x0165 Version 1.0
Configuration: 1
- Interfaces: 1 Bus Powered 98mA
Interface: 0
- Alternate Setting 0, Endpoints: 3
- Class Mass Storage, Transp. SCSI, Bulk only
- Endpoint 1 Out Bulk MaxPacket 512
- Endpoint 2 In Bulk MaxPacket 512
- Endpoint 3 In Interrupt MaxPacket 64 Interval 8ms

AMC1>
</syntaxhighlight>
 

== '''''fatload''''' ==
'''''fatload usb 0 ${loadaddr} u-boot.bin'''''
Load U-Boot image from USB mass storage device into RAM
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> fatload usb 0 ${loadaddr} u-boot.bin
reading u-boot.bin
379008 bytes read in 228 ms (1.6 MiB/s)
AMC1>
</syntaxhighlight>
 

== write to QSPI FLASH ==
'''''sf probe'''''
'''''sf erase 0x0 0x70000'''''
'''''sf write ${loadaddr} 0x0 ${filesize}'''''

Detect serial QSPI FLASH, erase boot sector and write new image
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1> sf erase 0x0 0x70000
SF: 458752 bytes @ 0x0 Erased: OK
AMC1> sf write ${loadaddr} 0x0 ${filesize}
device 0 offset 0x0, size 0x5c880
SF: 379008 bytes @ 0x0 Written: OK
AMC1>
</syntaxhighlight>
 

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[category:AMC1]]

Update U-Boot Image via TFTP on AMC1

2017-11-16T09:28:05Z

Claus:

__TOC__
__NOINDEX__

 
== Preparation ==
To update the U-Boot image located in serial FLASH via TFTP you need to do a proper network configuration first. Either enter all necessary environment variables manually on the U-Boot command prompt or use script [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]] to make all these settings automatically.

Required network settings: 
[[Network_settings_for_U-Boot_on_AMC1#ethaddr.2C_eth1addr|'''''eth1addr''''']] - own MAC address 
AMC1> setenv eth1addr c4:be:84:cb:1f:ff

[[Network_settings_for_U-Boot_on_AMC1#ipaddr|'''''ipaddr''''']] - own IP address 
AMC1> setenv ipaddr 192.168.168.197

[[Network_settings_for_U-Boot_on_AMC1#serverip|'''''serverip''''']] - remote server IP
AMC1> setenv serverip 192.168.168.158
 

== Load U-Boot image from TFTP server ==
If all network settings are correct, a new U-Boot image can be loaded from TFTP server:
tftpboot ${loadaddr} u-boot.bin

${loadaddr} is a pre-defined environment variable that specifies a free DDR RAM location for general purpose. We use it here as a temporary storage address for the TFTP transfer.

When the TFTP transfer succeeds, each received block (512 bytes) a '#' is printed on the terminal else a 'T' for timeout signals a problem connecting the server. A successful transmission can look like this (of course the IP addresses vary depending on your network configuration):

<syntaxhighlight lang=c style="border:1px dashed blue">
tftpboot ${loadaddr} u-boot.bin
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.196
Filename 'u-boot.bin'.
Load address: 0x80200000
Loading: #################################################################
########
981.4 KiB/s
done
Bytes transferred = 368880 (5a0f0 hex)
AMC1>
</syntaxhighlight>
 
== Serial FLASH programming ==
=== '''''sf probe''''' ===
First check if a serial FLASH is available:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
 
=== '''''sf erase''''' ===
If the probe command finds a serial FLASH, use the erase command to clear the U-Boot FLASH area:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf erase 0x0 0x70000
SF: 458752 bytes @ 0x0 Erased: OK
AMC1>
</syntaxhighlight>

{{warning|After erasing the FLASH boot area the AMC1 will not be bootable until a new boot image is written. Don't power cycle the board now}}
 
=== '''''sf write''''' ===

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf write ${loadaddr} 0x0 ${filesize}
device 0 offset 0x0, size 0x5a0f0
SF: 368880 bytes @ 0x0 Written: OK
AMC1>
</syntaxhighlight>

If the new U-Boot image was successfully written to the serial FLASH, your board will be bootable again.
 
== Script AMC1_UBootTFTPUpdate.ser ==
Use this script to do the above steps at once. Precondition is to run [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]] first.

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_UBootTFTPUpdate.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot configuration script for UBoot update per TFTP
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-09-07 12:43 PM
#
# Precondition: AMC1_NetConfig.ser must be executed first
#
# Environment variables and macros set in this script:
# ubootfile - U-Boot filename to load
# tftploaduboot - macro to execute tftpboot command
# tftpupdate - macro to execute all necessary steps
# savetospi - macro to write new U-Boot file to FLASH
# cleanup - macro to clean up environment
#
#######################################################################

# U-Boot filename to load, please change according to your filename
setenv ubootfile u-boot.bin

# macro to execute tftpboot command
setenv tftploaduboot 'tftpboot \\"${loadaddr}\\" \\"${ubootfile}\\"'

# macro to execute all necessary steps
setenv tftpupdate 'run netconf &&
if test -n \\"${serverip}\\"; then
true;
else
false;
fi && run tftploaduboot && run savetospi'

# macro to write new U-Boot file to FLASH
setenv savetospi 'sf probe && sf erase 0x0 0x70000 && sf write \\"${loadaddr}\\" 0x0 \\"${filesize}\\"'

# macro to clean up environment
setenv cleanup 'setenv ubootfile ; setenv tftploaduboot ; setenv tftpupdate ; setenv savetospi ; setenv cleanup ;'

# main script execution
run tftpupdate cleanup && echo success
</syntaxhighlight>

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Network settings for U-Boot on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[Category:AMC1]]
[[category:U-Boot]]

Serial FLASH programming via U-Boot on AMC1

2017-11-16T09:27:49Z

Claus:

__NOINDEX__

== '''''sf probe''''' ==
First check if a serial FLASH is available:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
 
== '''''sf erase''''' ==
If the probe command finds a serial FLASH, use the erase command to clear the U-Boot FLASH area:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf erase 0x0 0x70000
SF: 458752 bytes @ 0x0 Erased: OK
AMC1>
</syntaxhighlight>

{{warning|After erasing the FLASH boot area the AMC1 will not be bootable. Don't power cycle the board now}}
 
== '''''sf write''''' ==
'''''sf write''''' writes a previously loaded image (see [[Update U-Boot Image via TFTP on AMC1]]) from '''''${loadaddr}''''' in RAM to serial FLASH at address '''''0x0'''''

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf write ${loadaddr} 0x0 ${filesize}
device 0 offset 0x0, size 0x5a0f0
SF: 368880 bytes @ 0x0 Written: OK
AMC1>
</syntaxhighlight>

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Update U-Boot Image via TFTP on AMC1]]
on command prompt: AMC1> help sf

[[category:AMC1]]

Serial FLASH mapping on AMC1

2017-11-16T09:27:24Z

Claus:

__NOINDEX__

{| class="wikitable"
! style="font-weight: bold; font-style: italic;" | Address
! style="font-weight: bold; font-style: italic;" | Description
! style="font-weight: bold; font-style: italic;" | Notes
|-
| 0x000000
| U-Boot image
| required boot sector
|-
| 0x080000
| U-Boot image backup
| optional boot copy
|-
| 0x100000
| Environment
| used by '''''saveenv''''' command
|-
| 0x110000
| Environment backup
| optional backup of environment
|-
| 0x120000
| DTB
| optional
|-
| 0x130000
| free
| for general purpose
|-
|rowspan="2"| 0x200000 0x7FFFFF
|rowspan="2"| Linux Image
|rowspan="2"| optional Linux Image
|}

{{pagetop}}
== Additional Tags ==
[[Update U-Boot Image via TFTP on AMC1]]
[[Update U-Boot Image via USB on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[category:AMC1]]

Save DTB to serial FLASH on AMC1 via U-Boot

2017-11-16T09:27:05Z

Claus:

__NOINDEX__

== Load DTB ==
=== from TFTP server ===
Load a DTB image from TFTP server (correct network settings provided: [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]]):

'''''tftpboot ${fdtaddr} amc1.dtb'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> tftpboot ${fdtaddr} amc1.dtb
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.203
Filename 'amc1.dtb'.
Load address: 0x88000000
Loading: #########
641.6 KiB/s
done
Bytes transferred = 41451 (a1eb hex)
AMC1>
</syntaxhighlight>

=== from USB memory stick ===
==== '''''usb start''''' ====
<syntaxhighlight lang=c style="border:1px blue">
MC1> usb start
starting USB...
USB0: Register 2000440 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
AMC1>
</syntaxhighlight>

==== '''''fatload usb 0:1 ${fdtaddr} amc1.dtb''''' ====
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fatload usb 0:1 ${fdtaddr} amc1.dtb
reading amc1.dtb
41451 bytes read in 44 ms (919.9 KiB/s)
AMC1>
</syntaxhighlight>

=== from serial FLASH ===
If a DTB was previously saved somewhere in serial FLASH (e.g as backup), this image can be loaded
==== '''''sf probe''''' ====
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
==== '''''sf read ${fdtaddr} 0x150000 0x10000''''' ====

<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf read ${fdtaddr} 0x150000 0x10000
device 0 offset 0x150000, size 0x10000
SF: 65536 bytes @ 0x150000 Read: OK
AMC1>
</syntaxhighlight>
 

== Verify DTB ==
configure the fdt tool to point to the fdtaddr:
'''''fdt addr ${fdtaddr}'''''

If the DTB image is bad, you should get the error message:
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fdt addr ${fdtaddr}
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
AMC1>
</syntaxhighlight>

In case a valid DTB is found on the address, nothing is printed and you can proceed to list more details.
Enter '''''fdt header''''' command:
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fdt header
magic: 0xd00dfeed
totalsize: 0xa1eb (41451)
off_dt_struct: 0x38
off_dt_strings: 0x9a60
off_mem_rsvmap: 0x28
version: 17
last_comp_version: 16
boot_cpuid_phys: 0x0
size_dt_strings: 0x78b
size_dt_struct: 0x9a28
number mem_rsv: 0x0

AMC1>
</syntaxhighlight>

 
== Save to serial FLASH ==
=== Erase FLASH area ===
'''''sf erase 0x120000 0x10000'''''
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf erase 0x120000 0x10000
SF: 65536 bytes @ 0x120000 Erased: OK
AMC1>
</syntaxhighlight>

=== Write DTB to serial FLASH ===
'''''sf write ${fdtaddr} 0x120000 0x10000'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf write ${fdtaddr} 0x120000 0x10000
device 0 offset 0x120000, size 0x10000
SF: 65536 bytes @ 0x120000 Written: OK
AMC1>
</syntaxhighlight>
 
{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
[[Network settings for U-Boot on AMC1]]

[[category:AMC1]]

Reset U-Boot environment on AMC1

2017-11-16T09:26:51Z

Claus:

__NOINDEX__
== Reset AMC1 U-Boot environment ==
setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv

The script [[Reset_U-Boot_environment_on_AMC1#Script_AMC1_ClearEnvironment.ser|AMC1_ClearEnvironment.ser]] (s. below) is used to reset the AMC1 U-Boot environment. Use a serial terminal to send this script to your board. The script is executed automatically, no further commands are necessary. After the script succeeds, the AMC1 is re-bootet and you should see the following boot message:

<syntaxhighlight lang=c style="border:1px blue">
<debug_uart>

U-Boot 2017.01 (Aug 29 2017 - 13:35:23 +0200)

CPU : AM437X-GP rev 1.2
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
In: serial
Out: serial
Err: serial
Net: cpsw
Hit any key to stop autoboot: 0
========= D.SignT U-Boot first boot ==========
AMC1>
</syntaxhighlight>

No further program is booted and the U-Boot command processor is waiting for configuration steps. 

If you enter the print environment command '''''printenv''''', all factory settings will be displayed on your terminal:

<syntaxhighlight lang=c style="border:1px blue">
AMC1> printenv
arch=arm
autoconf=off
autoload=n
baudrate=115200
board=amc1
board_name=amc1
bootcmd=run firstboot;
bootdelay=2
bootm_size=0x20000000
console=ttyS2,115200n8
cpu=armv7
device=eth1
eth1addr=c4:be:84:cb:1f:ff
ethact=cpsw
ethaddr=c4:be:84:cb:1f:fd
fdt_addr_r=0x88000000
fdt_high=0xffffffff
fdtaddr=0x88000000
firstboot=echo ========= D.SignT U-Boot first boot ==========
hostname=AMC1-10004
kernel_addr_r=0x82000000
loadaddr=0x80200000
ramdisk_addr_r=0x88080000
rdaddr=0x88080000
soc=am33xx
stderr=serial
stdin=serial
stdout=serial
vendor=D.SignT GmbH & Co. KG

Environment size: 617/65532 bytes
AMC1>
</syntaxhighlight>
 {{pagetop}}
 

== '''''bootcmd''''' ==
The macro '''''bootcmd''''' is automatically executed when the U-Boot command processor is activated after boot. After executing AMC1_ClearEnvironment.ser the '''''bootcmd''''' is set to execute the '''''firstboot''''' macro which in turn prints the '''''========= D.SignT U-Boot first boot ==========''''' message after booting. To change the boot behaviour, you simply need to change the '''''bootcmd''''' environment variable to a reasonable boot macro.

{{pagetop}}
 

== Problems sending the script ==
You can either enter the commands by hand on your terminal or send the entire script at once via text file upload. Since the serial UART on the AMC1 uses a small cache and each command is interpreted after receiving a CR or LF immediately, it may happen that the one or the other line is broken. This may happen particularly if a long operation is in progress (e.g. a FLASH erase command). To avoid this situation all commands are usually stored as macros via '''''setenv''''' command and executed at the end of the script with the '''''run''''' command.

If you observe such broken lines despite this, you can add some delay after sending a line in your terminal. E.g. in TeraTerm:

[[File:TeraTermDelay.png|TeraTerm delay settings]]

{{pagetop}}
 

== Script AMC1_ClearEnvironment.ser ==
The full script is listed here:

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_ClearEnvironment.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot script to clear AMC1 U-Boot environment
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-08-29 01:42 PM
#
# This script resets and clears all U-Boot environment variables on the
# AMC1 to its default values and restarts the board with the clean en-
# vironment.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#! Warnings: !
#! - your network settings will be cleared and need to be reconfigured!
#! - your boot settings will be cleared and need to be set !
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# The environment space on the AMC1 is located in serial QSPI FLASH at
# address 0x100000 and is 0x10000 bytes large. If this script succeeds,
# only this specific area is erased and re-written with default values.
# No other space on eMMC or USB or I2C is affected.
#
# Variables after env default command:
# arch=arm
# autoconf=off
# baudrate=115200
# board=amc1
# board_name=amc1
# bootcmd=setenv autoload n; run nfsboot;
# bootdelay=2
# bootm_size=0x20000000
# console=ttyS2,115200n8
# cpu=armv7
# device=eth1
# fdt_addr_r=0x88000000
# fdt_high=0xffffffff
# fdtaddr=0x88000000
# kernel_addr_r=0x82000000
# loadaddr=0x80200000
# nfsboot=echo Booting from network disabled;
# ramdisk_addr_r=0x88080000
# rdaddr=0x88080000
# soc=am33xx
# vendor=D.SignT GmbH & Co. KG
#
# After reset some more variables are added:
# autoload=n
# eth1addr=c4:be:84:cb:1f:ff <- depends on chip ID
# ethact=cpsw
# ethaddr=c4:be:84:cb:1f:fd <- depends on chip ID
# hostname=AMC1-10004 <- depends on serial number
# stderr=serial
# stdin=serial
# stdout=serial
#
#######################################################################

setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv
</syntaxhighlight>
 {{pagetop}}
 

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
http://www.denx.de/wiki/U-Boot/TaskSetEnvironmentDefaults
http://processors.wiki.ti.com/index.php/Modifying_U-boot

[[category:U-Boot]]
[[Category:AMC1]]

Network settings for U-Boot on AMC1

2017-11-16T09:26:36Z

Claus:

__NOINDEX__
== U-Boot default network environment variables ==
=== '''''ethact''''' ===
Must be set to '''''cpsw''''' to enable the integrated switch. If this environment variable is cleared or set to anything else, the network will not be available.
 

=== '''''ethaddr, eth1addr''''' ===
MAC address for port 0 and port 1. During boot and if environment variable [[#ethact|'''''ethact''''']] is set to '''''cpsw''''' the chip internal MAC addresses are read and stored into these variables. If one of these variables is already set during boot, this variable will not be changed. Useful if a different MAC than the chip internal MAC address should be used (e.g a local administrated MAC starting with 02-00...).

If a Linux is booted from U-Boot, '''''ethaddr''''' and '''''eth1addr''''' are passed to Linux.
 

=== '''''ipaddr''''' ===
The local IP address used for all U-Boot Ethernet communication.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''netmask''''' ===
Local subnet mask.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''gatewayip''''' ===
Gateway IP address.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''dnsip''''' ===
DNS server IP for name resolution.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''serverip''''' ===
Used for '''''tftpboot''''' command to identify the TFTP server.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 
{{warning| The '''''dhcp''''' command will set this variable to the DHCP server address, '''NOT''' to your desired TFTP server address. Any time a '''''dhcp''''' command is executed, the '''''serverip''''' must be corrected to match your TFTP server address.}}
 
{{pagetop}}

== D.SignT network specific environment variables ==
=== '''''ipconfig''''' ===
A custom variable to distinguish a fix IP address setting from DHCP assigned addresses. Use value '''''fix''''' for a fixed IP address and '''''dhcp''''' for a dynamically assigned address.

Used in macro [[#netconf|'''''netconf''''']]
 

=== '''''tftpservername''''' ===
A optional custom variable to identify a TFTP server by its name. Requires a vaild DNS server Ip setting (s. [[#dnsip|'''''dnsip''''']] above).
 

=== '''''tftpserverip''''' ===
If the TFTP server IP address is known and will not change, this variable can be used to identify the TFTP server. Deactivate [[#tftpservername|'''''tftpservername''''']] in this case.
 

=== '''''nfsserverip''''' ===
If the NFS server IP address is known and will not change, this variable can be used to identify the NFS server. Deactivate [[#nfsservername|'''''nfsservername''''']] in this case.
 
{{pagetop}}

== D.SignT network specific macros ==
=== '''''netconf''''' ===
Macro '''''netconf''''' checks variable [[#ipconfig|'''''ipconfig''''']] and performs a DHCP request if configured for DHCP. If no IP address is assigned, a warning is issued.

If IP address assignment was successful, macros [[#settftpserver|'''''settftpserver''''']] and [[#setnfsserver|'''''setnfsserver''''']] are executed.
 

=== '''''settftpserver''''' ===
When a TFTP server is identified by its name via variable [[#tftpservername|'''''tftpservername''''']], this macro tries to resolve the IP address and if it succeeds variable [[#tftpserverip|'''''tftpserverip''''']] is set to the resolved address.
Additionally when this macro succeeds environment variable [[#serverip|'''''serverip''''']] is set to the resolved address and a '''''tftpboot''''' command should work.
 

=== '''''setnfsserver''''' ===
When a NFS server is identified by its name via variable [[#nfsservername|'''''nfsservername''''']], this macro tries to resolve the IP address and if it succeeds variable [[#nfsserverip|'''''nfsserverip''''']] is set to the resolved address.
 
{{pagetop}}
== Script AMC1_NetConfig.ser ==

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_NetConfig.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot configuration script for network settings
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-08-29 09:33 AM
#
# Change this script according to your network settings. It is re-
# commended to execute environment script AMC1_ClearEnvironment.ser to
# get a clean environment before.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#! Warning: !
#! - your network settings will be re-set !
#! - macro bootcmd is changed to execute netconf macro after boot !
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# Environment variables set in this script:
# ipaddr - either fix (192.168.168.77) or #dhcp
# tftpservername - TFTP server name (needs DNS resolution) or
# tftpserverip - TFTP server IP address
# ipconfig - fix or dhcp
# netmask - if IP address is fix
# gatewayip - if IP address is fix
# dnsip - if IP address is fix
# settftpserver - resolve TFTP server IP
# setnfsserver - resolve NFS server IP
# autosave - temporary variable to save environment
# netconf - macro to configure network environment
# bootcmd - is set to execute netconf
#
#######################################################################

# set ipaddr to #dhcp if dhcp is used else enter your desired IP:
# setenv ipaddr 192.168.168.77
setenv ipaddr #dhcp

# either set tftpservername or tftpserverip
setenv tftpservername sitara-sdk400
#setenv tftpserverip 192.168.168.158

# either set nfsservername or nfsserverip
setenv nfsservername sitara-sdk400
#setenv nfsserverip 192.168.168.158

# if ipaddr not configured for dhcp, set netmask and gateway manually
if test -n ${ipaddr}; then
setenv netmask 255.255.255.0;
setenv gatewayip 192.168.168.100;
setenv dnsip 192.168.168.100;
setenv ipconfig fix
else
setenv ipconfig dhcp
fi

setenv settftpserver '
if test -n \\"${tftpservername}\\"; then
dns \\"${tftpservername}\\" tftpserverip; true;
else
if test -z \\"${tftpserverip}\\"; then
echo TFTP server address could not be resolved; false;
else
true;
fi;
fi && setenv serverip \\"${tftpserverip}\\"'

setenv setnfsserver '
if test -n \\"${nfsservername}\\"; then
dns \\"${nfsservername}\\" nfsserverip; true;
else
if test -z \\"${nfsserverip}\\"; then
echo NFS server address could not be resolved; false;
else
true;
fi;
fi && setenv nfsserver \\"${nfsserverip}\\"'

setenv autosave 'setenv autosave ; setenv bootcmd run netconf; setenv firstboot ; saveenv'
setenv netconf '
if test \\"${ipconfig}\\" = dhcp; then
dhcp;
elif test -z ${ipaddr}; then
echo missing IP address settings; false;
else
true;
fi && run settftpserver setnfsserver'

run autosave netconf
</syntaxhighlight>
 {{pagetop}}
 
== Additional Tags ==
[[Reset U-Boot environment on AMC1]]
[[Backup and restore U-Boot environment on AMC1]]

[[category:U-Boot]]
[[Category:AMC1]]

Booting Linux from TFTP server on AMC1 with RFS on NFS

2017-11-16T09:26:17Z

Claus:

__NOINDEX__
== Preparation ==
To boot Linux via TFTP you need to do a proper network configuration first. Either enter all necessary environment variables manually on the U-Boot command prompt or use script [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]] to make all these settings automatically.

Required network settings: 
[[Network_settings_for_U-Boot_on_AMC1#ethaddr.2C_eth1addr|'''''eth1addr''''']] - own MAC address 
AMC1> setenv eth1addr c4:be:84:cb:1f:ff

[[Network_settings_for_U-Boot_on_AMC1#ipaddr|'''''ipaddr''''']] - own IP address 
AMC1> setenv ipaddr 192.168.168.197

[[Network_settings_for_U-Boot_on_AMC1#serverip|'''''serverip''''']] - remote server IP
AMC1> setenv serverip 192.168.168.158
 
== Load compressed Linux image from TFTP server ==
If all network settings are correct, a compressed Linux image can be loaded from TFTP server:
'''''tftpboot ${loadaddr} zImage-dsignt_amc1.bin'''''

${loadaddr} is a pre-defined environment variable that specifies a free DDR RAM location for general purpose. We use it here as a temporary storage address for the TFTP transfer.

When the TFTP transfer succeeds, each received block (512 bytes) a '#' is printed on the terminal else a 'T' for timeout signals a problem connecting the server. A successful transmission can look like this (of course the IP addresses vary depending on your network configuration):

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> tftpboot ${loadaddr} zImage-dsignt_amc1.bin
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.208
Filename 'zImage-dsignt_amc1.bin'.
Load address: 0x80200000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#############################################
1.3 MiB/s
done
Bytes transferred = 3555800 (3641d8 hex)
AMC1>
</syntaxhighlight>
 
== Load DTB from TFTP server ==
'''''tftpboot ${fdtaddr} amc1.dtb'''''
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> tftpboot ${fdtaddr} amc1.dtb
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.208
Filename 'amc1.dtb'.
Load address: 0x88000000
Loading: #########
663.1 KiB/s
done
Bytes transferred = 41451 (a1eb hex)
AMC1>
</syntaxhighlight>
 
== Set bootargs ==
The global environment variable '''''bootargs''''' is automatically passed to the booting Linux. Make sure '''''nfsroot''''' points to the valid NFS path on your NFS server:

'''''setenv bootargs root=/dev/nfs rw rootfstype=ext4 rootwait fixrtc nfsroot=${serverip}:/home/sitara/ti-processor-sdk-linux-am437x-evm-04.00.00.04/targetNFS,vers=3 ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${device}:${autoconf}'''''

In this case with installed SDK 04.00.00.04 tools on server ${serverip} the correct path is:
${serverip}:/home/sitara/ti-processor-sdk-linux-am437x-evm-04.00.00.04/targetNFS

 

== boot image ==
Boot Linux zImage:
'''''bootz ${loadaddr} - ${fdtaddr}'''''
 

{{pagetop}}

== Additional Tags ==
[[Network settings for U-Boot on AMC1]]

[[category:AMC1]]

Backup and restore U-Boot image on AMC1

2017-11-16T09:26:00Z

Claus:

__NOINDEX__
== Backup U-Boot image ==
Load U-Boot image to memory
'''''sf read ${loadaddr} 0x000000 0x80000'''''

Write to backup section
'''''sf write ${loadaddr} 0x080000 0x80000'''''

== Restore U-Boot image ==
Load U-Boot image from backup section
'''''sf read ${loadaddr} 0x080000 0x80000'''''

Write to U-Boot boot section section
'''''sf write ${loadaddr} 0x000000 0x80000'''''

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[category:AMC1]]

Backup and restore U-Boot environment on AMC1

2017-11-16T09:25:42Z

Claus:

__NOINDEX__
== Backup environment ==
Load environment from serial FLASH to RAM
'''''sf read ${loadaddr} 0x100000 0x10000'''''

Write to backup section
'''''sf erase 0x110000 0x10000'''''
'''''sf write ${loadaddr} 0x110000 0x10000'''''

== Restore environment ==
Load environment from backup section in serial FLASH to RAM
'''''sf read ${loadaddr} 0x110000 0x10000'''''

Write to environment section in serial FLASH
'''''sf erase 0x100000 0x10000'''''
'''''sf write ${loadaddr} 0x100000 0x10000'''''

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
[[Reset U-Boot environment on AMC1]]

[[category:AMC1]]

Booting Linux from TFTP server on AMC1 with RFS on NFS

2017-11-16T09:21:46Z

Claus: Claus moved page Booting Linux from TFTP server on AMC1 to Booting Linux from TFTP server on AMC1 with RFS on NFS without leaving a redirect

== Preparation ==
To boot Linux via TFTP you need to do a proper network configuration first. Either enter all necessary environment variables manually on the U-Boot command prompt or use script [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]] to make all these settings automatically.

Required network settings: 
[[Network_settings_for_U-Boot_on_AMC1#ethaddr.2C_eth1addr|'''''eth1addr''''']] - own MAC address 
AMC1> setenv eth1addr c4:be:84:cb:1f:ff

[[Network_settings_for_U-Boot_on_AMC1#ipaddr|'''''ipaddr''''']] - own IP address 
AMC1> setenv ipaddr 192.168.168.197

[[Network_settings_for_U-Boot_on_AMC1#serverip|'''''serverip''''']] - remote server IP
AMC1> setenv serverip 192.168.168.158
 
== Load compressed Linux image from TFTP server ==
If all network settings are correct, a compressed Linux image can be loaded from TFTP server:
'''''tftpboot ${loadaddr} zImage-dsignt_amc1.bin'''''

${loadaddr} is a pre-defined environment variable that specifies a free DDR RAM location for general purpose. We use it here as a temporary storage address for the TFTP transfer.

When the TFTP transfer succeeds, each received block (512 bytes) a '#' is printed on the terminal else a 'T' for timeout signals a problem connecting the server. A successful transmission can look like this (of course the IP addresses vary depending on your network configuration):

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> tftpboot ${loadaddr} zImage-dsignt_amc1.bin
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.208
Filename 'zImage-dsignt_amc1.bin'.
Load address: 0x80200000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#############################################
1.3 MiB/s
done
Bytes transferred = 3555800 (3641d8 hex)
AMC1>
</syntaxhighlight>
 
== Load DTB from TFTP server ==
'''''tftpboot ${fdtaddr} amc1.dtb'''''
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> tftpboot ${fdtaddr} amc1.dtb
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.208
Filename 'amc1.dtb'.
Load address: 0x88000000
Loading: #########
663.1 KiB/s
done
Bytes transferred = 41451 (a1eb hex)
AMC1>
</syntaxhighlight>
 
== Set bootargs ==
The global environment variable '''''bootargs''''' is automatically passed to the booting Linux. Make sure '''''nfsroot''''' points to the valid NFS path on your NFS server:

'''''setenv bootargs root=/dev/nfs rw rootfstype=ext4 rootwait fixrtc nfsroot=${serverip}:/home/sitara/ti-processor-sdk-linux-am437x-evm-04.00.00.04/targetNFS,vers=3 ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${device}:${autoconf}'''''

In this case with installed SDK 04.00.00.04 tools on server ${serverip} the correct path is:
${serverip}:/home/sitara/ti-processor-sdk-linux-am437x-evm-04.00.00.04/targetNFS

 

== boot image ==
Boot Linux zImage:
'''''bootz ${loadaddr} - ${fdtaddr}'''''
 

{{pagetop}}

== Additional Tags ==
[[Network settings for U-Boot on AMC1]]

[[category:AMC1]]

Category:AMC1

2017-11-15T11:43:36Z

Claus:

__HIDDENCAT__
__NOINDEX__

[[file:AMC1_main.png]]
 
== TI's starting portal ==
http://processors.wiki.ti.com/index.php/Sitara_AM437x_Portal

[[category:AMC]]

Backup and restore U-Boot environment on AMC1

2017-11-15T09:20:03Z

Claus:

== Backup environment ==
Load environment from serial FLASH to RAM
'''''sf read ${loadaddr} 0x100000 0x10000'''''

Write to backup section
'''''sf erase 0x110000 0x10000'''''
'''''sf write ${loadaddr} 0x110000 0x10000'''''

== Restore environment ==
Load environment from backup section in serial FLASH to RAM
'''''sf read ${loadaddr} 0x110000 0x10000'''''

Write to environment section in serial FLASH
'''''sf erase 0x100000 0x10000'''''
'''''sf write ${loadaddr} 0x100000 0x10000'''''

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
[[Reset U-Boot environment on AMC1]]

[[category:AMC1]]

Backup and restore U-Boot environment on AMC1

2017-11-15T09:19:40Z

Claus:

== Backup environment ==
Load environment from serial FLASH to RAM
'''''sf read ${loadaddr} 0x100000 0x10000'''''

Write to backup section
'''''sf erase 0x110000 0x10000'''''
'''''sf write ${loadaddr} 0x110000 0x10000'''''

== Restore environment ==
Load environment from backup section in serial FLASH to RAM
'''''sf read ${loadaddr} 0x110000 0x10000'''''

Write to environment section in serial FLASH
'''''sf erase 0x100000 0x10000'''''
'''''sf write ${loadaddr} 0x100000 0x10000'''''

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial_FLASH_programming_via_U-Boot_on_AMC1]]
[[Reset U-Boot environment on AMC1]]

[[category:AMC1]]

Update U-Boot Image via USB on AMC1

2017-11-15T09:16:13Z

Claus: Created page with " == '''''usb start''''' == '''''usb start''''' Initialize the USB controler and enumerate all USB devices <syntaxhighlight lang=c style="border:1px dashed blue"> AMC1> usb st..."

== '''''usb start''''' ==
'''''usb start'''''
Initialize the USB controler and enumerate all USB devices
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> usb start
starting USB...
USB0: Register 2000440 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
AMC1>
</syntaxhighlight>
 
'''''usb info'''''
Print detailed information of enumerated devices
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> usb info
1: Hub, USB Revision 3.0
- U-Boot XHCI Host Controller
- Class: Hub
- PacketSize: 9 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage, USB Revision 2.0
- USBest Technology USB Mass Storage Devie 1009135102477e
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x1307 Product 0x0165 Version 1.0
Configuration: 1
- Interfaces: 1 Bus Powered 98mA
Interface: 0
- Alternate Setting 0, Endpoints: 3
- Class Mass Storage, Transp. SCSI, Bulk only
- Endpoint 1 Out Bulk MaxPacket 512
- Endpoint 2 In Bulk MaxPacket 512
- Endpoint 3 In Interrupt MaxPacket 64 Interval 8ms

AMC1>
</syntaxhighlight>
 

== '''''fatload''''' ==
'''''fatload usb 0 ${loadaddr} u-boot.bin'''''
Load U-Boot image from USB mass storage device into RAM
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> fatload usb 0 ${loadaddr} u-boot.bin
reading u-boot.bin
379008 bytes read in 228 ms (1.6 MiB/s)
AMC1>
</syntaxhighlight>
 

== write to QSPI FLASH ==
'''''sf probe'''''
'''''sf erase 0x0 0x70000'''''
'''''sf write ${loadaddr} 0x0 ${filesize}'''''

Detect serial QSPI FLASH, erase boot sector and write new image
<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1> sf erase 0x0 0x70000
SF: 458752 bytes @ 0x0 Erased: OK
AMC1> sf write ${loadaddr} 0x0 ${filesize}
device 0 offset 0x0, size 0x5c880
SF: 379008 bytes @ 0x0 Written: OK
AMC1>
</syntaxhighlight>
 

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[category:AMC1]]

Update U-Boot Image via TFTP on AMC1

2017-11-15T09:15:37Z

Claus: Created page with "__TOC__ == Preparation == To update the U-Boot image located in serial FLASH via TFTP you need to do a proper network configuration first. Either enter all necessary envi..."

__TOC__
 
== Preparation ==
To update the U-Boot image located in serial FLASH via TFTP you need to do a proper network configuration first. Either enter all necessary environment variables manually on the U-Boot command prompt or use script [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]] to make all these settings automatically.

Required network settings: 
[[Network_settings_for_U-Boot_on_AMC1#ethaddr.2C_eth1addr|'''''eth1addr''''']] - own MAC address 
AMC1> setenv eth1addr c4:be:84:cb:1f:ff

[[Network_settings_for_U-Boot_on_AMC1#ipaddr|'''''ipaddr''''']] - own IP address 
AMC1> setenv ipaddr 192.168.168.197

[[Network_settings_for_U-Boot_on_AMC1#serverip|'''''serverip''''']] - remote server IP
AMC1> setenv serverip 192.168.168.158
 

== Load U-Boot image from TFTP server ==
If all network settings are correct, a new U-Boot image can be loaded from TFTP server:
tftpboot ${loadaddr} u-boot.bin

${loadaddr} is a pre-defined environment variable that specifies a free DDR RAM location for general purpose. We use it here as a temporary storage address for the TFTP transfer.

When the TFTP transfer succeeds, each received block (512 bytes) a '#' is printed on the terminal else a 'T' for timeout signals a problem connecting the server. A successful transmission can look like this (of course the IP addresses vary depending on your network configuration):

<syntaxhighlight lang=c style="border:1px dashed blue">
tftpboot ${loadaddr} u-boot.bin
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.196
Filename 'u-boot.bin'.
Load address: 0x80200000
Loading: #################################################################
########
981.4 KiB/s
done
Bytes transferred = 368880 (5a0f0 hex)
AMC1>
</syntaxhighlight>
 
== Serial FLASH programming ==
=== '''''sf probe''''' ===
First check if a serial FLASH is available:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
 
=== '''''sf erase''''' ===
If the probe command finds a serial FLASH, use the erase command to clear the U-Boot FLASH area:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf erase 0x0 0x70000
SF: 458752 bytes @ 0x0 Erased: OK
AMC1>
</syntaxhighlight>

{{warning|After erasing the FLASH boot area the AMC1 will not be bootable until a new boot image is written. Don't power cycle the board now}}
 
=== '''''sf write''''' ===

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf write ${loadaddr} 0x0 ${filesize}
device 0 offset 0x0, size 0x5a0f0
SF: 368880 bytes @ 0x0 Written: OK
AMC1>
</syntaxhighlight>

If the new U-Boot image was successfully written to the serial FLASH, your board will be bootable again.
 
== Script AMC1_UBootTFTPUpdate.ser ==
Use this script to do the above steps at once. Precondition is to run [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]] first.

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_UBootTFTPUpdate.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot configuration script for UBoot update per TFTP
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-09-07 12:43 PM
#
# Precondition: AMC1_NetConfig.ser must be executed first
#
# Environment variables and macros set in this script:
# ubootfile - U-Boot filename to load
# tftploaduboot - macro to execute tftpboot command
# tftpupdate - macro to execute all necessary steps
# savetospi - macro to write new U-Boot file to FLASH
# cleanup - macro to clean up environment
#
#######################################################################

# U-Boot filename to load, please change according to your filename
setenv ubootfile u-boot.bin

# macro to execute tftpboot command
setenv tftploaduboot 'tftpboot \\"${loadaddr}\\" \\"${ubootfile}\\"'

# macro to execute all necessary steps
setenv tftpupdate 'run netconf &&
if test -n \\"${serverip}\\"; then
true;
else
false;
fi && run tftploaduboot && run savetospi'

# macro to write new U-Boot file to FLASH
setenv savetospi 'sf probe && sf erase 0x0 0x70000 && sf write \\"${loadaddr}\\" 0x0 \\"${filesize}\\"'

# macro to clean up environment
setenv cleanup 'setenv ubootfile ; setenv tftploaduboot ; setenv tftpupdate ; setenv savetospi ; setenv cleanup ;'

# main script execution
run tftpupdate cleanup && echo success
</syntaxhighlight>

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Network settings for U-Boot on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[Category:AMC1]]
[[category:U-Boot]]

Serial FLASH programming via U-Boot on AMC1

2017-11-15T09:14:42Z

Claus: Created page with "== '''''sf probe''''' == First check if a serial FLASH is available: <syntaxhighlight lang=c style="border:1px dashed blue"> AMC1> sf probe SF: Detected w25q64cv with page si..."

== '''''sf probe''''' ==
First check if a serial FLASH is available:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
 
== '''''sf erase''''' ==
If the probe command finds a serial FLASH, use the erase command to clear the U-Boot FLASH area:

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf erase 0x0 0x70000
SF: 458752 bytes @ 0x0 Erased: OK
AMC1>
</syntaxhighlight>

{{warning|After erasing the FLASH boot area the AMC1 will not be bootable. Don't power cycle the board now}}
 
== '''''sf write''''' ==
'''''sf write''''' writes a previously loaded image (see [[Update U-Boot Image via TFTP on AMC1]]) from '''''${loadaddr}''''' in RAM to serial FLASH at address '''''0x0'''''

<syntaxhighlight lang=c style="border:1px dashed blue">
AMC1> sf write ${loadaddr} 0x0 ${filesize}
device 0 offset 0x0, size 0x5a0f0
SF: 368880 bytes @ 0x0 Written: OK
AMC1>
</syntaxhighlight>

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Update U-Boot Image via TFTP on AMC1]]
on command prompt: AMC1> help sf

[[category:AMC1]]

Save DTB to serial FLASH on AMC1 via U-Boot

2017-11-15T09:13:50Z

Claus: Created page with " == Load DTB == === from TFTP server === Load a DTB image from TFTP server (correct network settings provided: Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|..."

== Load DTB ==
=== from TFTP server ===
Load a DTB image from TFTP server (correct network settings provided: [[Network_settings_for_U-Boot_on_AMC1#Script_AMC1_NetConfig.ser|AMC1_NetConfig.ser]]):

'''''tftpboot ${fdtaddr} amc1.dtb'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> tftpboot ${fdtaddr} amc1.dtb
link up on port 1, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.168.158; our IP address is 192.168.168.203
Filename 'amc1.dtb'.
Load address: 0x88000000
Loading: #########
641.6 KiB/s
done
Bytes transferred = 41451 (a1eb hex)
AMC1>
</syntaxhighlight>

=== from USB memory stick ===
==== '''''usb start''''' ====
<syntaxhighlight lang=c style="border:1px blue">
MC1> usb start
starting USB...
USB0: Register 2000440 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
AMC1>
</syntaxhighlight>

==== '''''fatload usb 0:1 ${fdtaddr} amc1.dtb''''' ====
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fatload usb 0:1 ${fdtaddr} amc1.dtb
reading amc1.dtb
41451 bytes read in 44 ms (919.9 KiB/s)
AMC1>
</syntaxhighlight>

=== from serial FLASH ===
If a DTB was previously saved somewhere in serial FLASH (e.g as backup), this image can be loaded
==== '''''sf probe''''' ====
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf probe
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
AMC1>
</syntaxhighlight>
==== '''''sf read ${fdtaddr} 0x150000 0x10000''''' ====

<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf read ${fdtaddr} 0x150000 0x10000
device 0 offset 0x150000, size 0x10000
SF: 65536 bytes @ 0x150000 Read: OK
AMC1>
</syntaxhighlight>
 

== Verify DTB ==
configure the fdt tool to point to the fdtaddr:
'''''fdt addr ${fdtaddr}'''''

If the DTB image is bad, you should get the error message:
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fdt addr ${fdtaddr}
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
AMC1>
</syntaxhighlight>

In case a valid DTB is found on the address, nothing is printed and you can proceed to list more details.
Enter '''''fdt header''''' command:
<syntaxhighlight lang=c style="border:1px blue">
AMC1> fdt header
magic: 0xd00dfeed
totalsize: 0xa1eb (41451)
off_dt_struct: 0x38
off_dt_strings: 0x9a60
off_mem_rsvmap: 0x28
version: 17
last_comp_version: 16
boot_cpuid_phys: 0x0
size_dt_strings: 0x78b
size_dt_struct: 0x9a28
number mem_rsv: 0x0

AMC1>
</syntaxhighlight>

 
== Save to serial FLASH ==
=== Erase FLASH area ===
'''''sf erase 0x120000 0x10000'''''
<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf erase 0x120000 0x10000
SF: 65536 bytes @ 0x120000 Erased: OK
AMC1>
</syntaxhighlight>

=== Write DTB to serial FLASH ===
'''''sf write ${fdtaddr} 0x120000 0x10000'''''

<syntaxhighlight lang=c style="border:1px blue">
AMC1> sf write ${fdtaddr} 0x120000 0x10000
device 0 offset 0x120000, size 0x10000
SF: 65536 bytes @ 0x120000 Written: OK
AMC1>
</syntaxhighlight>
 
{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
[[Network settings for U-Boot on AMC1]]

[[category:AMC1]]

Network settings for U-Boot on AMC1

2017-11-15T09:13:05Z

Claus: Created page with "== U-Boot default network environment variables == === '''''ethact''''' === Must be set to '''''cpsw''''' to enable the integrated switch. If this environment variable is clea..."

== U-Boot default network environment variables ==
=== '''''ethact''''' ===
Must be set to '''''cpsw''''' to enable the integrated switch. If this environment variable is cleared or set to anything else, the network will not be available.
 

=== '''''ethaddr, eth1addr''''' ===
MAC address for port 0 and port 1. During boot and if environment variable [[#ethact|'''''ethact''''']] is set to '''''cpsw''''' the chip internal MAC addresses are read and stored into these variables. If one of these variables is already set during boot, this variable will not be changed. Useful if a different MAC than the chip internal MAC address should be used (e.g a local administrated MAC starting with 02-00...).

If a Linux is booted from U-Boot, '''''ethaddr''''' and '''''eth1addr''''' are passed to Linux.
 

=== '''''ipaddr''''' ===
The local IP address used for all U-Boot Ethernet communication.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''netmask''''' ===
Local subnet mask.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''gatewayip''''' ===
Gateway IP address.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''dnsip''''' ===
DNS server IP for name resolution.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 

=== '''''serverip''''' ===
Used for '''''tftpboot''''' command to identify the TFTP server.
{{note|Command '''''dhcp''''' will set this variable automatically, if a DHCP server is available and a vaild IP address was assigned.}}
 
{{warning| The '''''dhcp''''' command will set this variable to the DHCP server address, '''NOT''' to your desired TFTP server address. Any time a '''''dhcp''''' command is executed, the '''''serverip''''' must be corrected to match your TFTP server address.}}
 
{{pagetop}}

== D.SignT network specific environment variables ==
=== '''''ipconfig''''' ===
A custom variable to distinguish a fix IP address setting from DHCP assigned addresses. Use value '''''fix''''' for a fixed IP address and '''''dhcp''''' for a dynamically assigned address.

Used in macro [[#netconf|'''''netconf''''']]
 

=== '''''tftpservername''''' ===
A optional custom variable to identify a TFTP server by its name. Requires a vaild DNS server Ip setting (s. [[#dnsip|'''''dnsip''''']] above).
 

=== '''''tftpserverip''''' ===
If the TFTP server IP address is known and will not change, this variable can be used to identify the TFTP server. Deactivate [[#tftpservername|'''''tftpservername''''']] in this case.
 

=== '''''nfsserverip''''' ===
If the NFS server IP address is known and will not change, this variable can be used to identify the NFS server. Deactivate [[#nfsservername|'''''nfsservername''''']] in this case.
 
{{pagetop}}

== D.SignT network specific macros ==
=== '''''netconf''''' ===
Macro '''''netconf''''' checks variable [[#ipconfig|'''''ipconfig''''']] and performs a DHCP request if configured for DHCP. If no IP address is assigned, a warning is issued.

If IP address assignment was successful, macros [[#settftpserver|'''''settftpserver''''']] and [[#setnfsserver|'''''setnfsserver''''']] are executed.
 

=== '''''settftpserver''''' ===
When a TFTP server is identified by its name via variable [[#tftpservername|'''''tftpservername''''']], this macro tries to resolve the IP address and if it succeeds variable [[#tftpserverip|'''''tftpserverip''''']] is set to the resolved address.
Additionally when this macro succeeds environment variable [[#serverip|'''''serverip''''']] is set to the resolved address and a '''''tftpboot''''' command should work.
 

=== '''''setnfsserver''''' ===
When a NFS server is identified by its name via variable [[#nfsservername|'''''nfsservername''''']], this macro tries to resolve the IP address and if it succeeds variable [[#nfsserverip|'''''nfsserverip''''']] is set to the resolved address.
 
{{pagetop}}
== Script AMC1_NetConfig.ser ==

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_NetConfig.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot configuration script for network settings
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-08-29 09:33 AM
#
# Change this script according to your network settings. It is re-
# commended to execute environment script AMC1_ClearEnvironment.ser to
# get a clean environment before.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#! Warning: !
#! - your network settings will be re-set !
#! - macro bootcmd is changed to execute netconf macro after boot !
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# Environment variables set in this script:
# ipaddr - either fix (192.168.168.77) or #dhcp
# tftpservername - TFTP server name (needs DNS resolution) or
# tftpserverip - TFTP server IP address
# ipconfig - fix or dhcp
# netmask - if IP address is fix
# gatewayip - if IP address is fix
# dnsip - if IP address is fix
# settftpserver - resolve TFTP server IP
# setnfsserver - resolve NFS server IP
# autosave - temporary variable to save environment
# netconf - macro to configure network environment
# bootcmd - is set to execute netconf
#
#######################################################################

# set ipaddr to #dhcp if dhcp is used else enter your desired IP:
# setenv ipaddr 192.168.168.77
setenv ipaddr #dhcp

# either set tftpservername or tftpserverip
setenv tftpservername sitara-sdk400
#setenv tftpserverip 192.168.168.158

# either set nfsservername or nfsserverip
setenv nfsservername sitara-sdk400
#setenv nfsserverip 192.168.168.158

# if ipaddr not configured for dhcp, set netmask and gateway manually
if test -n ${ipaddr}; then
setenv netmask 255.255.255.0;
setenv gatewayip 192.168.168.100;
setenv dnsip 192.168.168.100;
setenv ipconfig fix
else
setenv ipconfig dhcp
fi

setenv settftpserver '
if test -n \\"${tftpservername}\\"; then
dns \\"${tftpservername}\\" tftpserverip; true;
else
if test -z \\"${tftpserverip}\\"; then
echo TFTP server address could not be resolved; false;
else
true;
fi;
fi && setenv serverip \\"${tftpserverip}\\"'

setenv setnfsserver '
if test -n \\"${nfsservername}\\"; then
dns \\"${nfsservername}\\" nfsserverip; true;
else
if test -z \\"${nfsserverip}\\"; then
echo NFS server address could not be resolved; false;
else
true;
fi;
fi && setenv nfsserver \\"${nfsserverip}\\"'

setenv autosave 'setenv autosave ; setenv bootcmd run netconf; setenv firstboot ; saveenv'
setenv netconf '
if test \\"${ipconfig}\\" = dhcp; then
dhcp;
elif test -z ${ipaddr}; then
echo missing IP address settings; false;
else
true;
fi && run settftpserver setnfsserver'

run autosave netconf
</syntaxhighlight>
 {{pagetop}}
 
== Additional Tags ==
[[Reset U-Boot environment on AMC1]]
[[Backup and restore U-Boot environment on AMC1]]

[[category:U-Boot]]
[[Category:AMC1]]

Booting Linux from TFTP server on AMC1 with RFS on NFS

2017-11-15T09:12:21Z

Claus: Created page with "== Preparation == To boot Linux via TFTP you need to do a proper network configuration first. Either enter all necessary environment variables manually on the U-Boot command p..."

Backup and restore U-Boot image on AMC1

2017-11-15T09:11:27Z

Claus: Created page with "== Backup U-Boot image == Load U-Boot image to memory '''''sf read ${loadaddr} 0x000000 0x80000''''' Write to backup section '''''sf write ${loadaddr} 0x080000 0x80000''''..."

== Backup U-Boot image ==
Load U-Boot image to memory
'''''sf read ${loadaddr} 0x000000 0x80000'''''

Write to backup section
'''''sf write ${loadaddr} 0x080000 0x80000'''''

== Restore U-Boot image ==
Load U-Boot image from backup section
'''''sf read ${loadaddr} 0x080000 0x80000'''''

Write to U-Boot boot section section
'''''sf write ${loadaddr} 0x000000 0x80000'''''

{{pagetop}}

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[category:AMC1]]

Reset U-Boot environment on AMC1

2017-11-15T09:10:10Z

Claus:

== Reset AMC1 U-Boot environment ==
setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv

The script [[Reset_U-Boot_environment_on_AMC1#Script_AMC1_ClearEnvironment.ser|AMC1_ClearEnvironment.ser]] (s. below) is used to reset the AMC1 U-Boot environment. Use a serial terminal to send this script to your board. The script is executed automatically, no further commands are necessary. After the script succeeds, the AMC1 is re-bootet and you should see the following boot message:

<syntaxhighlight lang=c style="border:1px blue">
<debug_uart>

U-Boot 2017.01 (Aug 29 2017 - 13:35:23 +0200)

CPU : AM437X-GP rev 1.2
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
In: serial
Out: serial
Err: serial
Net: cpsw
Hit any key to stop autoboot: 0
========= D.SignT U-Boot first boot ==========
AMC1>
</syntaxhighlight>

No further program is booted and the U-Boot command processor is waiting for configuration steps. 

If you enter the print environment command '''''printenv''''', all factory settings will be displayed on your terminal:

<syntaxhighlight lang=c style="border:1px blue">
AMC1> printenv
arch=arm
autoconf=off
autoload=n
baudrate=115200
board=amc1
board_name=amc1
bootcmd=run firstboot;
bootdelay=2
bootm_size=0x20000000
console=ttyS2,115200n8
cpu=armv7
device=eth1
eth1addr=c4:be:84:cb:1f:ff
ethact=cpsw
ethaddr=c4:be:84:cb:1f:fd
fdt_addr_r=0x88000000
fdt_high=0xffffffff
fdtaddr=0x88000000
firstboot=echo ========= D.SignT U-Boot first boot ==========
hostname=AMC1-10004
kernel_addr_r=0x82000000
loadaddr=0x80200000
ramdisk_addr_r=0x88080000
rdaddr=0x88080000
soc=am33xx
stderr=serial
stdin=serial
stdout=serial
vendor=D.SignT GmbH & Co. KG

Environment size: 617/65532 bytes
AMC1>
</syntaxhighlight>
 {{pagetop}}
 

== '''''bootcmd''''' ==
The macro '''''bootcmd''''' is automatically executed when the U-Boot command processor is activated after boot. After executing AMC1_ClearEnvironment.ser the '''''bootcmd''''' is set to execute the '''''firstboot''''' macro which in turn prints the '''''========= D.SignT U-Boot first boot ==========''''' message after booting. To change the boot behaviour, you simply need to change the '''''bootcmd''''' environment variable to a reasonable boot macro.

{{pagetop}}
 

== Problems sending the script ==
You can either enter the commands by hand on your terminal or send the entire script at once via text file upload. Since the serial UART on the AMC1 uses a small cache and each command is interpreted after receiving a CR or LF immediately, it may happen that the one or the other line is broken. This may happen particularly if a long operation is in progress (e.g. a FLASH erase command). To avoid this situation all commands are usually stored as macros via '''''setenv''''' command and executed at the end of the script with the '''''run''''' command.

If you observe such broken lines despite this, you can add some delay after sending a line in your terminal. E.g. in TeraTerm:

[[File:TeraTermDelay.png|TeraTerm delay settings]]

{{pagetop}}
 

== Script AMC1_ClearEnvironment.ser ==
The full script is listed here:

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_ClearEnvironment.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot script to clear AMC1 U-Boot environment
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-08-29 01:42 PM
#
# This script resets and clears all U-Boot environment variables on the
# AMC1 to its default values and restarts the board with the clean en-
# vironment.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#! Warnings: !
#! - your network settings will be cleared and need to be reconfigured!
#! - your boot settings will be cleared and need to be set !
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# The environment space on the AMC1 is located in serial QSPI FLASH at
# address 0x100000 and is 0x10000 bytes large. If this script succeeds,
# only this specific area is erased and re-written with default values.
# No other space on eMMC or USB or I2C is affected.
#
# Variables after env default command:
# arch=arm
# autoconf=off
# baudrate=115200
# board=amc1
# board_name=amc1
# bootcmd=setenv autoload n; run nfsboot;
# bootdelay=2
# bootm_size=0x20000000
# console=ttyS2,115200n8
# cpu=armv7
# device=eth1
# fdt_addr_r=0x88000000
# fdt_high=0xffffffff
# fdtaddr=0x88000000
# kernel_addr_r=0x82000000
# loadaddr=0x80200000
# nfsboot=echo Booting from network disabled;
# ramdisk_addr_r=0x88080000
# rdaddr=0x88080000
# soc=am33xx
# vendor=D.SignT GmbH & Co. KG
#
# After reset some more variables are added:
# autoload=n
# eth1addr=c4:be:84:cb:1f:ff <- depends on chip ID
# ethact=cpsw
# ethaddr=c4:be:84:cb:1f:fd <- depends on chip ID
# hostname=AMC1-10004 <- depends on serial number
# stderr=serial
# stdin=serial
# stdout=serial
#
#######################################################################

setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv
</syntaxhighlight>
 {{pagetop}}
 

== Additional Tags ==
[[Serial FLASH mapping on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]
http://www.denx.de/wiki/U-Boot/TaskSetEnvironmentDefaults
http://processors.wiki.ti.com/index.php/Modifying_U-boot

[[category:U-Boot]]
[[Category:AMC1]]

Reset U-Boot environment on AMC1

2017-11-15T09:09:47Z

Claus: Claus moved page Reset U-Boot environment to Reset U-Boot environment on AMC1 without leaving a redirect

== Reset AMC1 U-Boot environment ==
setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv

The script [[Reset_U-Boot_environment#Script AMC1_ClearEnvironment.ser|AMC1_ClearEnvironment.ser]] (s. below) is used to reset the AMC1 U-Boot environment. Use a serial terminal to send this script to your board. The script is executed automatically, no further commands are necessary. After the script succeeds, the AMC1 is re-bootet and you should see the following boot message:

<syntaxhighlight lang=c style="border:1px blue">
<debug_uart>

U-Boot 2017.01 (Aug 29 2017 - 13:35:23 +0200)

CPU : AM437X-GP rev 1.2
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
In: serial
Out: serial
Err: serial
Net: cpsw
Hit any key to stop autoboot: 0
========= D.SignT U-Boot first boot ==========
AMC1>
</syntaxhighlight>

No further program is booted and the U-Boot command processor is waiting for configuration steps. 

If you enter the print environment command '''''printenv''''', all factory settings will be displayed on your terminal:

<syntaxhighlight lang=c style="border:1px blue">
AMC1> printenv
arch=arm
autoconf=off
autoload=n
baudrate=115200
board=amc1
board_name=amc1
bootcmd=run firstboot;
bootdelay=2
bootm_size=0x20000000
console=ttyS2,115200n8
cpu=armv7
device=eth1
eth1addr=c4:be:84:cb:1f:ff
ethact=cpsw
ethaddr=c4:be:84:cb:1f:fd
fdt_addr_r=0x88000000
fdt_high=0xffffffff
fdtaddr=0x88000000
firstboot=echo ========= D.SignT U-Boot first boot ==========
hostname=AMC1-10004
kernel_addr_r=0x82000000
loadaddr=0x80200000
ramdisk_addr_r=0x88080000
rdaddr=0x88080000
soc=am33xx
stderr=serial
stdin=serial
stdout=serial
vendor=D.SignT GmbH & Co. KG

Environment size: 617/65532 bytes
AMC1>
</syntaxhighlight>
 {{pagetop}}
 

== '''''bootcmd''''' ==
The macro '''''bootcmd''''' is automatically executed when the U-Boot command processor is activated after boot. After executing AMC1_ClearEnvironment.ser the '''''bootcmd''''' is set to execute the '''''firstboot''''' macro which in turn prints the '''''========= D.SignT U-Boot first boot ==========''''' message after booting. To change the boot behaviour, you simply need to change the '''''bootcmd''''' environment variable to a reasonable boot macro.

{{pagetop}}
 

== Problems sending the script ==
You can either enter the commands by hand on your terminal or send the entire script at once via text file upload. Since the serial UART on the AMC1 uses a small cache and each command is interpreted after receiving a CR or LF immediately, it may happen that the one or the other line is broken. This may happen particularly if a long operation is in progress (e.g. a FLASH erase command). To avoid this situation all commands are usually stored as macros via '''''setenv''''' command and executed at the end of the script with the '''''run''''' command.

If you observe such broken lines despite this, you can add some delay after sending a line in your terminal. E.g. in TeraTerm:

[[File:TeraTermDelay.png|TeraTerm delay settings]]

{{pagetop}}
 

== Script AMC1_ClearEnvironment.ser ==
The full script is listed here:

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_ClearEnvironment.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot script to clear AMC1 U-Boot environment
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-08-29 01:42 PM
#
# This script resets and clears all U-Boot environment variables on the
# AMC1 to its default values and restarts the board with the clean en-
# vironment.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#! Warnings: !
#! - your network settings will be cleared and need to be reconfigured!
#! - your boot settings will be cleared and need to be set !
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# The environment space on the AMC1 is located in serial QSPI FLASH at
# address 0x100000 and is 0x10000 bytes large. If this script succeeds,
# only this specific area is erased and re-written with default values.
# No other space on eMMC or USB or I2C is affected.
#
# Variables after env default command:
# arch=arm
# autoconf=off
# baudrate=115200
# board=amc1
# board_name=amc1
# bootcmd=setenv autoload n; run nfsboot;
# bootdelay=2
# bootm_size=0x20000000
# console=ttyS2,115200n8
# cpu=armv7
# device=eth1
# fdt_addr_r=0x88000000
# fdt_high=0xffffffff
# fdtaddr=0x88000000
# kernel_addr_r=0x82000000
# loadaddr=0x80200000
# nfsboot=echo Booting from network disabled;
# ramdisk_addr_r=0x88080000
# rdaddr=0x88080000
# soc=am33xx
# vendor=D.SignT GmbH & Co. KG
#
# After reset some more variables are added:
# autoload=n
# eth1addr=c4:be:84:cb:1f:ff <- depends on chip ID
# ethact=cpsw
# ethaddr=c4:be:84:cb:1f:fd <- depends on chip ID
# hostname=AMC1-10004 <- depends on serial number
# stderr=serial
# stdin=serial
# stdout=serial
#
#######################################################################

setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv
</syntaxhighlight>
 {{pagetop}}
 

== Additional Tags ==
[[AMC1 serial FLASH mapping]]
[[AMC1 U-Boot: serial FLASH programming]]
http://www.denx.de/wiki/U-Boot/TaskSetEnvironmentDefaults
http://processors.wiki.ti.com/index.php/Modifying_U-boot

[[category:U-Boot]]
[[Category:AMC1]]

Backup and restore U-Boot environment on AMC1

2017-11-15T09:09:02Z

Claus:

Backup and restore U-Boot environment on AMC1

2017-11-15T09:08:44Z

Claus: Claus moved page Backup and restore AMC1 U-Boot environment to Backup and restore U-Boot environment on AMC1 without leaving a redirect

== Backup environment ==
Load environment from serial FLASH to RAM
'''''sf read ${loadaddr} 0x100000 0x10000'''''

Write to backup section
'''''sf erase 0x110000 0x10000'''''
'''''sf write ${loadaddr} 0x110000 0x10000'''''

== Restore environment ==
Load environment from backup section in serial FLASH to RAM
'''''sf read ${loadaddr} 0x110000 0x10000'''''

Write to environment section in serial FLASH
'''''sf erase 0x100000 0x10000'''''
'''''sf write ${loadaddr} 0x100000 0x10000'''''

{{pagetop}}

== Additional Tags ==
[[AMC1 serial FLASH mapping]]
[[AMC1 U-Boot: serial FLASH programming]]
[[Reset U-Boot environment]]

[[category:AMC1]]

Serial FLASH mapping on AMC1

2017-11-15T09:07:45Z

Claus:

{| class="wikitable"
! style="font-weight: bold; font-style: italic;" | Address
! style="font-weight: bold; font-style: italic;" | Description
! style="font-weight: bold; font-style: italic;" | Notes
|-
| 0x000000
| U-Boot image
| required boot sector
|-
| 0x080000
| U-Boot image backup
| optional boot copy
|-
| 0x100000
| Environment
| used by '''''saveenv''''' command
|-
| 0x110000
| Environment backup
| optional backup of environment
|-
| 0x120000
| DTB
| optional
|-
| 0x130000
| free
| for general purpose
|-
|rowspan="2"| 0x200000 0x7FFFFF
|rowspan="2"| Linux Image
|rowspan="2"| optional Linux Image
|}

{{pagetop}}
== Additional Tags ==
[[Update U-Boot Image via TFTP on AMC1]]
[[Update U-Boot Image via USB on AMC1]]
[[Serial FLASH programming via U-Boot on AMC1]]

[[category:AMC1]]

Serial FLASH mapping on AMC1

2017-11-15T09:07:25Z

Claus: Claus moved page AMC1 serial FLASH mapping to Serial FLASH mapping on AMC1 without leaving a redirect

{| class="wikitable"
! style="font-weight: bold; font-style: italic;" | Address
! style="font-weight: bold; font-style: italic;" | Description
! style="font-weight: bold; font-style: italic;" | Notes
|-
| 0x000000
| U-Boot image
| required boot sector
|-
| 0x080000
| U-Boot image backup
| optional boot copy
|-
| 0x100000
| Environment
| used by '''''saveenv''''' command
|-
| 0x110000
| Environment backup
| optional backup of environment
|-
| 0x120000
| DTB
| optional
|-
| 0x130000
| free
| for general purpose
|-
|rowspan="2"| 0x200000 0x7FFFFF
|rowspan="2"| Linux Image
|rowspan="2"| optional Linux Image
|}

{{pagetop}}
== Additional Tags ==
[[AMC1 U-Boot: Update via TFTP]]
[[AMC1 U-Boot: Update via USB]]
[[AMC1 U-Boot: serial FLASH programming]]

[[category:AMC1]]

Backup and restore U-Boot environment on AMC1

2017-11-15T08:18:30Z

Claus:

== Backup environment ==
Load environment from serial FLASH to RAM
'''''sf read ${loadaddr} 0x100000 0x10000'''''

Write to backup section
'''''sf erase 0x110000 0x10000'''''
'''''sf write ${loadaddr} 0x110000 0x10000'''''

== Restore environment ==
Load environment from backup section in serial FLASH to RAM
'''''sf read ${loadaddr} 0x110000 0x10000'''''

Write to environment section in serial FLASH
'''''sf erase 0x100000 0x10000'''''
'''''sf write ${loadaddr} 0x100000 0x10000'''''

{{pagetop}}

== Additional Tags ==
[[AMC1 serial FLASH mapping]]
[[AMC1 U-Boot: serial FLASH programming]]
[[Reset U-Boot environment]]

[[category:AMC1]]

Backup and restore U-Boot environment on AMC1

2017-11-15T08:17:26Z

Claus: Created page with "== Backup environment == Load environment from serial FLASH to RAM '''''sf read ${loadaddr} 0x100000 0x10000''''' Write to backup section '''''sf erase 0x110000 0x10000''''..."

== Backup environment ==
Load environment from serial FLASH to RAM
'''''sf read ${loadaddr} 0x100000 0x10000'''''

Write to backup section
'''''sf erase 0x110000 0x10000'''''
'''''sf write ${loadaddr} 0x110000 0x10000'''''

== Restore environment ==
Load environment from backup section in serial FLASH to RAM
'''''sf read ${loadaddr} 0x110000 0x10000'''''

Write to environment section in serial FLASH
'''''sf erase 0x100000 0x10000'''''
'''''sf write ${loadaddr} 0x100000 0x10000'''''

{{pagetop}}

== Additional Tags ==
[[AMC1 U-Boot: serial FLASH mapping]]
[[AMC1 U-Boot: serial FLASH programming]]
[[AMC1 U-Boot: Reset U-Boot environment]]

[[category:AMC1]]

Reset U-Boot environment on AMC1

2017-11-15T08:15:39Z

Claus:

Serial FLASH mapping on AMC1

2017-11-15T08:14:29Z

Claus: Created page with "{| class="wikitable" ! style="font-weight: bold; font-style: italic;" | Address ! style="font-weight: bold; font-style: italic;" | Description ! style="font-weight: bold; font..."

{| class="wikitable"
! style="font-weight: bold; font-style: italic;" | Address
! style="font-weight: bold; font-style: italic;" | Description
! style="font-weight: bold; font-style: italic;" | Notes
|-
| 0x000000
| U-Boot image
| required boot sector
|-
| 0x080000
| U-Boot image backup
| optional boot copy
|-
| 0x100000
| Environment
| used by '''''saveenv''''' command
|-
| 0x110000
| Environment backup
| optional backup of environment
|-
| 0x120000
| DTB
| optional
|-
| 0x130000
| free
| for general purpose
|-
|rowspan="2"| 0x200000 0x7FFFFF
|rowspan="2"| Linux Image
|rowspan="2"| optional Linux Image
|}

{{pagetop}}
== Additional Tags ==
[[AMC1 U-Boot: Update via TFTP]]
[[AMC1 U-Boot: Update via USB]]
[[AMC1 U-Boot: serial FLASH programming]]

[[category:AMC1]]

File:TeraTermDelay.png

2017-11-15T08:11:41Z

Claus:

MediaWiki:Breadcrumbs

2017-11-15T08:10:23Z

Claus:

Reset U-Boot environment on AMC1

2017-11-15T08:07:41Z

Claus:

== Reset AMC1 U-Boot environment ==
setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv

The script [[Reset_U-Boot_environment#Script AMC1_ClearEnvironment.ser|AMC1_ClearEnvironment.ser]] (s. below) is used to reset the AMC1 U-Boot environment. Use a serial terminal to send this script to your board. The script is executed automatically, no further commands are necessary. After the script succeeds, the AMC1 is re-bootet and you should see the following boot message:

<syntaxhighlight lang=c style="border:1px blue">
<debug_uart>

U-Boot 2017.01 (Aug 29 2017 - 13:35:23 +0200)

CPU : AM437X-GP rev 1.2
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
In: serial
Out: serial
Err: serial
Net: cpsw
Hit any key to stop autoboot: 0
========= D.SignT U-Boot first boot ==========
AMC1>
</syntaxhighlight>

No further program is booted and the U-Boot command processor is waiting for configuration steps. 

If you enter the print environment command '''''printenv''''', all factory settings will be displayed on your terminal:

<syntaxhighlight lang=c style="border:1px blue">
AMC1> printenv
arch=arm
autoconf=off
autoload=n
baudrate=115200
board=amc1
board_name=amc1
bootcmd=run firstboot;
bootdelay=2
bootm_size=0x20000000
console=ttyS2,115200n8
cpu=armv7
device=eth1
eth1addr=c4:be:84:cb:1f:ff
ethact=cpsw
ethaddr=c4:be:84:cb:1f:fd
fdt_addr_r=0x88000000
fdt_high=0xffffffff
fdtaddr=0x88000000
firstboot=echo ========= D.SignT U-Boot first boot ==========
hostname=AMC1-10004
kernel_addr_r=0x82000000
loadaddr=0x80200000
ramdisk_addr_r=0x88080000
rdaddr=0x88080000
soc=am33xx
stderr=serial
stdin=serial
stdout=serial
vendor=D.SignT GmbH & Co. KG

Environment size: 617/65532 bytes
AMC1>
</syntaxhighlight>
 {{pagetop}}
 

== '''''bootcmd''''' ==
The macro '''''bootcmd''''' is automatically executed when the U-Boot command processor is activated after boot. After executing AMC1_ClearEnvironment.ser the '''''bootcmd''''' is set to execute the '''''firstboot''''' macro which in turn prints the '''''========= D.SignT U-Boot first boot ==========''''' message after booting. To change the boot behaviour, you simply need to change the '''''bootcmd''''' environment variable to a reasonable boot macro.

{{pagetop}}
 

== Problems sending the script ==
You can either enter the commands by hand on your terminal or send the entire script at once via text file upload. Since the serial UART on the AMC1 uses a small cache and each command is interpreted after receiving a CR or LF immediately, it may happen that the one or the other line is broken. This may happen particularly if a long operation is in progress (e.g. a FLASH erase command). To avoid this situation all commands are usually stored as macros via '''''setenv''''' command and executed at the end of the script with the '''''run''''' command.

If you observe such broken lines despite this, you can add some delay after sending a line in your terminal. E.g. in TeraTerm:

[[File:TeraTermDelay.png|TeraTerm delay settings]]

{{pagetop}}
 

== Script AMC1_ClearEnvironment.ser ==
The full script is listed here:

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_ClearEnvironment.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot script to clear AMC1 U-Boot environment
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-08-29 01:42 PM
#
# This script resets and clears all U-Boot environment variables on the
# AMC1 to its default values and restarts the board with the clean en-
# vironment.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#! Warnings: !
#! - your network settings will be cleared and need to be reconfigured!
#! - your boot settings will be cleared and need to be set !
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# The environment space on the AMC1 is located in serial QSPI FLASH at
# address 0x100000 and is 0x10000 bytes large. If this script succeeds,
# only this specific area is erased and re-written with default values.
# No other space on eMMC or USB or I2C is affected.
#
# Variables after env default command:
# arch=arm
# autoconf=off
# baudrate=115200
# board=amc1
# board_name=amc1
# bootcmd=setenv autoload n; run nfsboot;
# bootdelay=2
# bootm_size=0x20000000
# console=ttyS2,115200n8
# cpu=armv7
# device=eth1
# fdt_addr_r=0x88000000
# fdt_high=0xffffffff
# fdtaddr=0x88000000
# kernel_addr_r=0x82000000
# loadaddr=0x80200000
# nfsboot=echo Booting from network disabled;
# ramdisk_addr_r=0x88080000
# rdaddr=0x88080000
# soc=am33xx
# vendor=D.SignT GmbH & Co. KG
#
# After reset some more variables are added:
# autoload=n
# eth1addr=c4:be:84:cb:1f:ff <- depends on chip ID
# ethact=cpsw
# ethaddr=c4:be:84:cb:1f:fd <- depends on chip ID
# hostname=AMC1-10004 <- depends on serial number
# stderr=serial
# stdin=serial
# stdout=serial
#
#######################################################################

setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv
</syntaxhighlight>
 {{pagetop}}
 

== Additional Tags ==
[[AMC1 U-Boot: serial FLASH mapping]]
[[AMC1 U-Boot: serial FLASH programming]]
http://www.denx.de/wiki/U-Boot/TaskSetEnvironmentDefaults
http://processors.wiki.ti.com/index.php/Modifying_U-boot

[[category:U-Boot]]
[[Category:AMC1]]

Reset U-Boot environment on AMC1

2017-11-15T07:58:16Z

Claus: Created page with "== Reset AMC1 U-Boot environment == setenv resetenv 'env default -f -a && saveenv && reset' run resetenv The script Reset U-Boot environment#Script AMC1_ClearEnviro..."

== Reset AMC1 U-Boot environment ==
setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv

The script [[Reset U-Boot environment#Script AMC1_ClearEnvironment.ser|AMC1_ClearEnvironment.ser]] (s. below) is used to reset the AMC1 U-Boot environment. Use a serial terminal to send this script to your board. The script is executed automatically, no further commands are necessary. After the script succeeds, the AMC1 is re-bootet and you should see the following boot message:

<syntaxhighlight lang=c style="border:1px blue">
<debug_uart>

U-Boot 2017.01 (Aug 29 2017 - 13:35:23 +0200)

CPU : AM437X-GP rev 1.2
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected w25q64cv with page size 256 Bytes, erase size 4 KiB, total 8 MiB, m
apped at 30000000
In: serial
Out: serial
Err: serial
Net: cpsw
Hit any key to stop autoboot: 0
========= D.SignT U-Boot first boot ==========
AMC1>
</syntaxhighlight>

No further program is booted and the U-Boot command processor is waiting for configuration steps. 

If you enter the print environment command '''''printenv''''', all factory settings will be displayed on your terminal:

<syntaxhighlight lang=c style="border:1px blue">
AMC1> printenv
arch=arm
autoconf=off
autoload=n
baudrate=115200
board=amc1
board_name=amc1
bootcmd=run firstboot;
bootdelay=2
bootm_size=0x20000000
console=ttyS2,115200n8
cpu=armv7
device=eth1
eth1addr=c4:be:84:cb:1f:ff
ethact=cpsw
ethaddr=c4:be:84:cb:1f:fd
fdt_addr_r=0x88000000
fdt_high=0xffffffff
fdtaddr=0x88000000
firstboot=echo ========= D.SignT U-Boot first boot ==========
hostname=AMC1-10004
kernel_addr_r=0x82000000
loadaddr=0x80200000
ramdisk_addr_r=0x88080000
rdaddr=0x88080000
soc=am33xx
stderr=serial
stdin=serial
stdout=serial
vendor=D.SignT GmbH & Co. KG

Environment size: 617/65532 bytes
AMC1>
</syntaxhighlight>
 {{pagetop}}
 

== '''''bootcmd''''' ==
The macro '''''bootcmd''''' is automatically executed when the U-Boot command processor is activated after boot. After executing AMC1_ClearEnvironment.ser the '''''bootcmd''''' is set to execute the '''''firstboot''''' macro which in turn prints the '''''========= D.SignT U-Boot first boot ==========''''' message after booting. To change the boot behaviour, you simply need to change the '''''bootcmd''''' environment variable to a reasonable boot macro.

{{pagetop}}
 

== Problems sending the script ==
You can either enter the commands by hand on your terminal or send the entire script at once via text file upload. Since the serial UART on the AMC1 uses a small cache and each command is interpreted after receiving a CR or LF immediately, it may happen that the one or the other line is broken. This may happen particularly if a long operation is in progress (e.g. a FLASH erase command). To avoid this situation all commands are usually stored as macros via '''''setenv''''' command and executed at the end of the script with the '''''run''''' command.

If you observe such broken lines despite this, you can add some delay after sending a line in your terminal. E.g. in TeraTerm:

[[File:TeraTermDelay.png|TeraTerm delay settings]]

{{pagetop}}
 

== Script AMC1_ClearEnvironment.ser ==
The full script is listed here:

<syntaxhighlight lang=c style="border:1px dashed blue">
###################################################################//##
#
# @file AMC1_ClearEnvironment.ser
# @verbatim _ _ _
# __| | ___(_) ____ _ __ | |_
# / _` | / __| |/ _` | '_ \| __|
# | (_| | _ \__ \ | (_| | | | | |_
# \__,_|(_) ___/_|\__, |_| |_|\__|
# Signalprocessing |___/ Technology
# @endverbatim
# @brief U-Boot script to clear AMC1 U-Boot environment
# @author D.SignT GmbH & Co. KG, Claus Hermbusche
# @date 2017-08-29 01:42 PM
#
# This script resets and clears all U-Boot environment variables on the
# AMC1 to its default values and restarts the board with the clean en-
# vironment.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#! Warnings: !
#! - your network settings will be cleared and need to be reconfigured!
#! - your boot settings will be cleared and need to be set !
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# The environment space on the AMC1 is located in serial QSPI FLASH at
# address 0x100000 and is 0x10000 bytes large. If this script succeeds,
# only this specific area is erased and re-written with default values.
# No other space on eMMC or USB or I2C is affected.
#
# Variables after env default command:
# arch=arm
# autoconf=off
# baudrate=115200
# board=amc1
# board_name=amc1
# bootcmd=setenv autoload n; run nfsboot;
# bootdelay=2
# bootm_size=0x20000000
# console=ttyS2,115200n8
# cpu=armv7
# device=eth1
# fdt_addr_r=0x88000000
# fdt_high=0xffffffff
# fdtaddr=0x88000000
# kernel_addr_r=0x82000000
# loadaddr=0x80200000
# nfsboot=echo Booting from network disabled;
# ramdisk_addr_r=0x88080000
# rdaddr=0x88080000
# soc=am33xx
# vendor=D.SignT GmbH & Co. KG
#
# After reset some more variables are added:
# autoload=n
# eth1addr=c4:be:84:cb:1f:ff <- depends on chip ID
# ethact=cpsw
# ethaddr=c4:be:84:cb:1f:fd <- depends on chip ID
# hostname=AMC1-10004 <- depends on serial number
# stderr=serial
# stdin=serial
# stdout=serial
#
#######################################################################

setenv resetenv 'env default -f -a && saveenv && reset'
run resetenv
</syntaxhighlight>
 {{pagetop}}
 

== Additional Tags ==
[[AMC1 U-Boot: serial FLASH mapping]]
[[AMC1 U-Boot: serial FLASH programming]]
http://www.denx.de/wiki/U-Boot/TaskSetEnvironmentDefaults
http://processors.wiki.ti.com/index.php/Modifying_U-boot

[[category:U-Boot]]
[[Category:AMC1]]

File:AMC1 main.png

2017-11-15T07:51:20Z

Claus:

Category:AMC1

2017-11-15T07:49:22Z

Claus: Created page with "file:AMC1_main.png == TI's starting portal == http://processors.wiki.ti.com/index.php/Sitara_AM437x_Portal category:AMC"

[[file:AMC1_main.png]]
 
== TI's starting portal ==
http://processors.wiki.ti.com/index.php/Sitara_AM437x_Portal

[[category:AMC]]

Force same COM port assignment to all D.Module2.C6657

2017-11-08T13:13:34Z

Claus: Claus moved page Force same COM port assignment to all D.Module.C6657 to Force same COM port assignment to all D.Module2.C6657 without leaving a redirect

== Problem ==
When a new D.Module2.C6657 is connected via USB to your PC, a new free COM port is automatically assigned by the installation wizard. If this default behavior is not suitable because an application needs to be controlled always by a fixed port, a user could follow [[Re-assign_virtual_COM_port|Re-assign virtual COM port]] to manually change the COM port for a specific device or use the instructions below to permanently change this behavior for all D.Module2.C6657.

{{pagetop}}
== Solution ==
The automatic new COM port assignment is caused by a unique serial number programmed into the FTDI chips on all D.Module2.C6657 boards. With a specific registry switch all D.Module2.C6657 FTDI serial numbers can be excluded from the default automatic COM port assignment. Create a '''''REG_BINARY''''' value '''''IgnoreHWSerNum04036015''''' set to '''''01''''' under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags

or use the following .reg script to add the key to your registry:

<syntaxhighlight lang="c">
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags]
"IgnoreHWSerNum04036015"=hex:01
</syntaxhighlight>

{{note|It might be necessary to follow [[Re-assign_virtual_COM_port|Re-assign virtual COM port]] to initially assign a specific port}}

{{pagetop}}
== Additional Tags ==
http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%20COM%20Ports_Are%20Allocated%20on%20Driver_Installation.pdf

[[category:D.Module2.C6657]]

Force same COM port assignment to all D.Module2.C6657

2017-11-08T06:59:59Z

Claus: Created page with "== Problem == When a new D.Module2.C6657 is connected via USB to your PC, a new free COM port is automatically assigned by the installation wizard. If this default behavior is..."

MediaWiki:Common.css

2017-10-09T15:10:05Z

Claus:

/*
This is the CSS for all skins (for all users) on MediaWiki.org.

SECTIONS:
1. Indication of namespaces
2. Color classes for content
3. Special pages
4. Main page styling
5. Sidebar external links
6. Extension:Matrix stuff
7. Wikitables, infobox templates, warnings, and other such stylings
8. Some other small things
*/
/*

/* changes D.SignT: new design */
/*
.mw-body
{
position: relative;
top: 6em;
}
*/

div#content
{
top: 9em;
/* margin-left:1.4em; */
margin-top: 25px;
min-width:877px;
min-height:69%;
margin-right: 1.25em;
border-right-width:1px;
}

div#column-content
{
/* height: 120%; */
margin-bottom: 7em;
}
/*
div#footer
{
margin: 0 6em 0 0
}
*/
/*
#bodyContent{margin-left: 12em;padding-left:2em;
margin-top: 2em;width:auto; min-width: 680px;}
*/
/*
li#ca-nstab-mediawiki,li#ca-nstab-category,li#ca-nstab-project,li#ca-nstab-main, li#ca-viewsource,li#ca-history,li#ca-edit,li#ca-push,li#ca-delete,li#ca-move,li#ca-protect,li#ca-watch,li#ca-unwatch {
position: relative; top: 6em;
}
*/
li#ca-viewsource,li#ca-history,li#ca-talk
{
/* position: relative; top: 6em; */
display:none;
}
#p-logo a, #p-logo a:hover
{
width:100%;
height:88px;
margin-left: 136px;
margin-top: 33px;
margin-bottom: 20px;
}
#p-logo
{
width:24em;
margin-bottom: 20px;
}

#p-cactions
{
top: 10em;
}
#p-personal
{
top: 5px;
}
/*
div#mw-panel {
position: absolute;
top: 100px;
width: 20em;
left: 0;
}
*/
h2 {
/* font-size: 180%; */
font-weight: bold;
}
/* h3 {
font-size: 145%;
font-weight: normal;
} */
/* extra buttons for edit dialog (from commons:MediaWiki:Common.css) */
.my-buttons {
padding: .5em;
}
.my-buttons a {
color: black;
background-color: #cde !important;
font-weight: bold;
font-size: .9em;
text-decoration: none;
border: thin #069 outset;
padding: 0 .1em .1em;
}
.my-buttons a:hover, .my-buttons a:active {
background-color: #bcd;
border-style: inset;
}

/* from [[User:Splarka/Help:Linked images]] */
.imagelink_wikilogo a {
width: 335px;
height: 135px;
display: block;
text-decoration: none;
background-image: url("//upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png");
}

/**
* CharInsert extension
*/
.mw-charinsert-buttons {
margin-top: 10px;
border: 1px solid #aaaaaa;
padding: 1px;
text-align: center;
font-size: 110%;
}
.mw-charinsert-buttons a {
color: black;
background-color: #cde !important;
font-weight: bold;
font-size: .9em;
text-decoration: none;
border: thin #069 outset;
padding: 0 .1em .1em;
}
.mw-charinsert-buttons a:hover,
.mw-charinsert-buttons a:active {
background-color: #bcd;
border-style: inset;
}
.client-js .mw-edittools-section {
display: inline;
}
.client-js .mw-edittools-section input[type="button"] {
font-size: 0.9em;
padding-left: 1px;
padding-right: 1px;
margin-left: 1px;
}

/* remove Toolbox */
#p-tb {
display:none !important;
}

/* ms@forty-four.de: Tab-Reiter ausgeblendet */
/* li#ca-viewsource,li#ca-history,li#ca-talk{display:none;} */
/*
body.page-Main_Page.action-view table{
display: none;
}
*/

MediaWiki:Common.css

2017-09-19T14:28:33Z

Claus:

/*
This is the CSS for all skins (for all users) on MediaWiki.org.

SECTIONS:
1. Indication of namespaces
2. Color classes for content
3. Special pages
4. Main page styling
5. Sidebar external links
6. Extension:Matrix stuff
7. Wikitables, infobox templates, warnings, and other such stylings
8. Some other small things
*/
/*

/* changes D.SignT: new design */
/*
.mw-body
{
position: relative;
top: 6em;
}
*/
div#content
{
top: 9em;
/* margin-left:1.4em; */
margin-top: 25px;
min-width:877px;
min-height:69%;
margin-right: 1.25em;
border-right-width:1px;
}

div#column-content
{
/* height: 120%; */
margin-bottom: 7em;
}
/*
div#footer
{
margin: 0 6em 0 0
}
*/
/*
#bodyContent{margin-left: 12em;padding-left:2em;
margin-top: 2em;width:auto; min-width: 680px;}
*/
/*
li#ca-nstab-mediawiki,li#ca-nstab-category,li#ca-nstab-project,li#ca-nstab-main, li#ca-viewsource,li#ca-history,li#ca-edit,li#ca-push,li#ca-delete,li#ca-move,li#ca-protect,li#ca-watch,li#ca-unwatch {
position: relative; top: 6em;
}
*/
li#ca-viewsource,li#ca-history,li#ca-talk
{
/* position: relative; top: 6em; */
display:none;
}
#p-logo a, #p-logo a:hover
{
width:100%;
height:88px;
margin-left: 136px;
margin-top: 33px;
margin-bottom: 20px;
}
#p-logo
{
width:24em;
margin-bottom: 20px;
}

#p-cactions
{
top: 10em;
}
#p-personal
{
top: 5px;
}
/*
div#mw-panel {
position: absolute;
top: 100px;
width: 20em;
left: 0;
}
*/
h2 {
/* font-size: 180%; */
font-weight: bold;
}
/* h3 {
font-size: 145%;
font-weight: normal;
} */
/* extra buttons for edit dialog (from commons:MediaWiki:Common.css) */
.my-buttons {
padding: .5em;
}
.my-buttons a {
color: black;
background-color: #cde !important;
font-weight: bold;
font-size: .9em;
text-decoration: none;
border: thin #069 outset;
padding: 0 .1em .1em;
}
.my-buttons a:hover, .my-buttons a:active {
background-color: #bcd;
border-style: inset;
}

/* from [[User:Splarka/Help:Linked images]] */
.imagelink_wikilogo a {
width: 335px;
height: 135px;
display: block;
text-decoration: none;
background-image: url("//upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png");
}

/**
* CharInsert extension
*/
.mw-charinsert-buttons {
margin-top: 10px;
border: 1px solid #aaaaaa;
padding: 1px;
text-align: center;
font-size: 110%;
}
.mw-charinsert-buttons a {
color: black;
background-color: #cde !important;
font-weight: bold;
font-size: .9em;
text-decoration: none;
border: thin #069 outset;
padding: 0 .1em .1em;
}
.mw-charinsert-buttons a:hover,
.mw-charinsert-buttons a:active {
background-color: #bcd;
border-style: inset;
}
.client-js .mw-edittools-section {
display: inline;
}
.client-js .mw-edittools-section input[type="button"] {
font-size: 0.9em;
padding-left: 1px;
padding-right: 1px;
margin-left: 1px;
}

/* remove Toolbox */
#p-tb {
display:none !important;
}

/* ms@forty-four.de: Tab-Reiter ausgeblendet */
/* li#ca-viewsource,li#ca-history,li#ca-talk{display:none;} */
/*
body.page-Main_Page.action-view table{
display: none;
}
*/