PythonQ 248-8XX Spécifications Page 87
- Page / 210
- Table des matières
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
7.5.1. Bootlog of tftp'd Linux kernel with Root Filesystem over NFS◊
7.6. Boot from NAND Flash Memory♦
7.7. Standalone Operation with Ramdisk Image♦
7. Booting Embedded Linux
7.1. Introduction
In principle, if you have a Linux kernel image and the flattened device tree blob somewhere in system
memory (RAM, ROM, flash...), then all you need to boot the system is the bootm command. Assume a
Linux kernel image has been stored at address 0x42000000 and the flattened device tree blob has been stored
at address 0x41000000 - then you can boot this image with the following command:
=> bootm 42000000 - 41000000
7.2. Flattened Device Tree Blob
Linux kernel expects certain information on the hardware that it runs on. For kernels compiled with fdt
support, this information has the form of a device tree, which is based on the Open Firmware specification.
Bootloaders like U-Boot that do not implement the Open Firmware API, are expected to pass to the kernel a
binary form of the flattened device tree, commonly referred to as FDT blob or simply the blob.
Device trees are defined in human-readable text files, which are part of the Linux 2.6 source tree. Device tree
source for the m28 board is found in arch/arm/boot/dts/m28.dts file. Before the device tree can be
passed to the kernel, it has to be compiled to the binary form by the dtc compiler. The dtc compiler is
included with the Linux kernel since 2.6.25. Since 2.6.26 there is also a simple makefile rule to generate the
blob:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- m28.dtb
After the blob has been compiled, it has to be transferred from where it was built
("arch/arm/boot/m28.dtb") to target's memory, for example over the TFTP protocol using U-Boot's
tftp command. Then, the blob is passed to the kernel by the bootm command, and its address in memory is
one of the arguments to bootm - refer to the description of this command in UBootCmdGroupExec for more
details.
Note that U-Boot makes some automatic modifications to the blob before passing it to the kernel - mainly
adding and modifying information that is learnt at run-time. See the board-specific function ft_board_setup()
and related routines.
U-Boot also has provisions to alter a flattened device tree in arbitrary ways from the command line, refer to
the description of the fdt commands found in UBootCmdFDT.
Notes:
Flattened Device Tree custodian's page at http://www.denx.de/wiki/U-Boot/UBootFdtInfo contains
useful information, and a number of references.
•
At the time of this writing (September 2007) blob handling is still a very fresh feature and undergoing
frequent changes. Reader is encouraged to watch the u-boot-users and linuxppc-dev mailing
lists for important news (required version of the dtc compiler, blob compilation options, flattened
•
7.2. Flattened Device Tree Blob 87
- 1. Abstract 6
- 2. Introduction 7
- 3.1. ELDK Availability 10
- 3.2. ELDK Getting Help 10
- 3.3. Supported Host Systems 10
- 3.5. Installation 11
- 3.5.1. Product Packaging 11
- 3.5.2. Downloading the ELDK 11
- 3.5.3. Initial Installation 12
- Packages 13
- 3.6. Working with ELDK 14
- $ arm-linux-gcc -c myfile.c 15
- 3.9. ELDK Packages 18
- 3.10.3. build.sh Usage 28
- 4. System Setup 30
- 4.8. Configuring a NFS Server 34
- 5. Das U-Boot 36
- 5.1. Current Versions 36
- 5.3. Configuration 37
- 5.4. Installation 38
- 5.4.1. Before You Begin 38
- 5.5. Tool Installation 39
- 5.6. Initialization 39
- 5.7. Initial Steps 40
- 5.8. The First Power-On 41
- 5.9.1. Information Commands 42
- 5.9.2. Memory Commands 44
- 5.9.2.3. cmp - memory compare 45
- 5.9.2.4. cp - memory copy 46
- 5.9.2.5. md - memory display 46
- 5.9.3. Flash Memory Commands 50
- 5.9.3.6. UBI Usage in U-Boot 54
- Useful definitions: 58
- 5.9.5. Download Commands 61
- 5.9.9. Storage devices 72
- 5.9.9.1. MMC devices 72
- 5.9.8. Special Commands 72
- 5.9.9.1. MMC devices 74 74
- 5.9.9.1. MMC devices 75 75
- 5.9.9.2. NAND devices 76
- 5.13. U-Boot Image Formats 84
- 5.14.1. Boot Count Limit 84
- 6.3. Installation 86
- 7. Booting Embedded Linux 87
- 7.1. Introduction 87
- 7.3. Passing Kernel Arguments 88
- 7.4. Boot Arguments Unleashed 88
- 8. Building and Using Modules 96
- 9. Advanced Topics 97
- 9.1. Flash Filesystems 97
- 9.1.3. Second Version of JFFS 99
- 9.1.5.1. Create Device Files 101
- 9.2.1. Mount Parameters 107
- $ mkfs.jffs2 -U \ 114
- Using FEC ETHERNET device 115
- Load address: 0x100000 115
- => printenv addip 115
- /proc on /proc type proc (rw) 116
- FAT File System 121
- 9.7. Overlay File Systems 126
- What it is good for? 127
- Examples 127
- # insmod mini_fo.o 128
- Performance overhead 128
- Further information 129
- 9.8.1. Mount Parameters 129
- 9.8.2. Example 129
- 10. Debugging 130
- 10.1. Debugging of U-Boot 130
- 10.2. Linux Kernel Debugging 131
- 10.4. Tips and Tricks 135
- 10.5. Application Debugging 135
- 10.5.2. Remote Debugging 136
- 12.1. Application Notes 137
- 12.2. Further Reading 137
- 12.2.2. Linux kernel 138
- Articles 138
- Standards: 139
- 12.2.4. Network Programming 139
- 12.2.10. Embedded Topics 141
- 12.3. Mailing Lists 142
- 12.4. Links 142
- 12.5. Tools 143
- 13. Appendix 143
- 13.1. Flat Device Tree 144 144
- 13.1. Flat Device Tree 145 145
- 13.1. Flat Device Tree 146 146
- ELDK Installation Hangs 151
- 14.1.11. Enable SSH Access 158
- 14.2. U-Boot 159
- -mrelocatable 160
- Compiler 164
- 14.2.12. Erasing Flash Fails 165
- $ make tools/gen_eth_addr 166
- $ tools/gen_eth_addr 166
- 14.2.17.2. Hush shell 169
- 14.2.17.3. Hush shell scripts 170
- 14.2.17.4. General rules 171
- => setenv clocks_in_mhz 1 173
- => saveenv 173
- => setenv clocks_in_mhz 173
- Rebooting in 1 seconds 178
- # cat /etc/blank_off 181
- # cat /etc/init_tty 181
- Multi-File Image 183
- 14.3.26.1. XIP Kernel 191
- 14.3.26.2. Cramfs Filesystem 192
- 14.3.26.3. Hints and Notes 193
- 14.3.30. Swapping over NFS 196
- 14.4. Self 198
- 14.5. RTAI 200
- 14.6. BDI2000 201
- 14.7. Motorola LITE5200 Board 203
- 15. Glossary 204
- YellowDog 210
Produits connexes et manuels pour Système de soudage PythonQ 248-8XX
Delta Electronics BCB1012EH manuels
Manuels d'utilisation et guides de l'utilisateur pour Ventilateurs Delta Electronics BCB1012EH.
Nous fournissons des manuels en pdf 1 Delta Electronics BCB1012EH à télécharger gratuitement par type de document : Manuel de l'utilisateur
Delta electronics BCB1012EH Manuel de l'utilisateur (1 pages)
marque: Delta-electronics | Catégorie: Fans | Taille: 0.77 MB |
Table des matières
Plus de produits et de manuels pour Ventilateurs Delta Electronics
| Modèles | Type de document |
|---|---|
| FFB0412GHN |
Manuel de l'utilisateur
Delta Electronics FFB0412GHN User Manual,
1 pages
|
| NFB1212H |
Manuel de l'utilisateur
Delta Electronics NFB1212H User Manual,
1 pages
|
| EFB Series |
Manuel de l'utilisateur
Delta Electronics EFB Series User Manual,
1 pages
|
| KFB1724SHS |
Manuel de l'utilisateur
Delta Electronics KFB1724SHS User Manual,
1 pages
|
| 92 x 92 x 15 MM Series |
Manuel de l'utilisateur
Delta Electronics 92 x 92 x 15 MM Series User Manual,
1 pages
|
| EFB0612HHA |
Manuel de l'utilisateur
Delta Electronics EFB0612HHA User Manual,
1 pages
|
| BFB1212HH |
Manuel de l'utilisateur
Delta Electronics BFB1212HH User Manual,
3 pages
|
| GFB0812SHG |
Manuel de l'utilisateur
Delta Electronics GFB0812SHG User Manual,
1 pages
|
| FFB0612DHE |
Manuel de l'utilisateur
Delta Electronics FFB0612DHE User Manual,
1 pages
|
| GFB0812DHU |
Manuel de l'utilisateur
Delta Electronics GFB0812DHU User Manual,
1 pages
|
| FFB0612UHE |
Manuel de l'utilisateur
Delta Electronics FFB0612UHE User Manual,
1 pages
|
| FFB0412EHN |
Manuel de l'utilisateur
Delta Electronics FFB0412EHN User Manual,
1 pages
|
© 2020, manymanuals.fr. Tous droits réservés | 0.035 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels