Taskit ARM9 CPU-module with Linux Stamp9261-series Stamp9261 (64F/64R) 542310 Data Sheet
Product codes
542310
Linux Guide
taskit GmbH
Address-based removal of write protection, recreation of starting configuration. When
using address-based protect commands, please note that the beginning and ending
address are exactly on the sector border.
using address-based protect commands, please note that the beginning and ending
address are exactly on the sector border.
U-Boot> protect off 10000000 103fffff
Un-Protected 71 sectors
Un-Protected 71 sectors
U-Boot> flinfo
Bank # 1: AMD Chip: LV320B 32 Mbit
Bank # 1: AMD Chip: LV320B 32 Mbit
Size: 4 MB in 71 Sectors
Sector Start Addresses:
Sector Start Addresses:
10000000 10002000 10004000 10006000 10008000
1000A000 1000C000 1000E000 10010000 10020000
1000A000 1000C000 1000E000 10010000 10020000
10030000 10040000 10050000 10060000 10070000
. . .
103A0000 103B0000 103C0000 103D0000 103E0000
103F0000
U-Boot> protect on 10000000 1002ffff
U-Boot> protect on 10000000 1002ffff
Protected 10 sectors
U-Boot> flinfo
U-Boot> flinfo
Bank # 1: AMD Chip: LV320B 32 Mbit
Sector Start Addresses:
Sector Start Addresses:
Size: 4 MB in 71 Sectors
10000000 (RO) 10002000 (RO) 10004000 (RO) 10006000 (RO) 10008000 (RO)
10000000 (RO) 10002000 (RO) 10004000 (RO) 10006000 (RO) 10008000 (RO)
1000A000 (RO) 1000C000 (RO) 1000E000 (RO) 10010000 (RO) 10020000 (RO)
10030000 10040000 10050000 10060000 10070000
10030000 10040000 10050000 10060000 10070000
. . .
103A0000 103B0000 103C0000 103D0000 103E0000
103F0000
103F0000
erase - erase FLASH memory
erase addr1 addr2
erase all
erase all
You can delete flash sectors using the erase command. Write-protected sectors are not
erased. As with the protect command, the sector borders must be observed exactly. Call
erase all to erase all known flash modules.
erased. As with the protect command, the sector borders must be observed exactly. Call
erase all to erase all known flash modules.
For example: Deleting the 3
rd
MB of the flash module
U-Boot> erase 10200000 102FFFFF
flash_erase: first: 39 last: 54
flash_erase: first: 39 last: 54
Erased 16 sectors
11.6.2. Load programs and files via the serial interface or Ethernet
The commands bootp, dhcp and rarpboot all work according to an identical principal.
They attempt to get valid IP parameters via the corresponding protocol (DHCP, BOOTP or
RARP), in order to load a specified file from the network to an address, using TFTP.
tftpboot and nfs expect that the IP parameters are already set; loadb loads a file via the
serial interface using Kermit. In order to be able to use the commands for dynamic address
assignment, the DHCP server must be configured properly in the network in order to
deliver the IP address of the TFTP server, for example. If no specific IP address is
returned, the DHCP server sends its own IP address instead. Here is a host statement for
They attempt to get valid IP parameters via the corresponding protocol (DHCP, BOOTP or
RARP), in order to load a specified file from the network to an address, using TFTP.
tftpboot and nfs expect that the IP parameters are already set; loadb loads a file via the
serial interface using Kermit. In order to be able to use the commands for dynamic address
assignment, the DHCP server must be configured properly in the network in order to
deliver the IP address of the TFTP server, for example. If no specific IP address is
returned, the DHCP server sends its own IP address instead. Here is a host statement for
Page 58 of 65
Version 1.26
(2008-04-30)