Address
text field during the flashing process (step #6).
mem=64M console=ttyS0,115200 root=/dev/mtdblock1 rw rootfstype=jffs2which leads to the following u-boot command to setup the environment :
setenv bootargs 'mem=64M console=ttyS0,115200 root=/dev/mtdblock1 rw rootfstype=jffs2' saveenvOnce the Linux kernel and root filesystem loaded, you can access the Linux console through the serial line plugged on DBGU port.
root
login account without password.
ANGSTROM_EXTRA_INSTAL
variable. Basically this is exactly the same thing as extending the RDEPENDS
variable (Cf. x11-at91sam9-image.bb recipe):
RDEPENDS = "\ [..] ${ANGSTROM_EXTRA_INSTALL}"Check the attached
x11-at91sam9-image.bb
file.
ANGSTROM_EXTRA_INSTALL += " \ <package_name> \ <another_package_or_task> \ <..> \ "The complete process of how to build the rootfs is described in the How to build Angstrom for AT91 from sources chapter. This point is discussed in details in this acticle : The correct way to add packages to an OpenEmbedded Image.
/etc/opkg
, /etc/opkg/*.conf
files points towards the servers where the device can pull packages from.
Angstrom feeds are discussed in the Angstrom Wiki.
Information on available packages are stored on particular files: the Packages
or Packages.gz
. This kind of file is downloaded to the target while issuing the opkg update
command. tmp/deploy/glibc/ipk/armv5te
.
If you build additional packages, do not forget to run bitbake package-index
to update Packages
and Packages.gz
files in your opkg feed.
bitbake package-index
path_to_deploy_dir/glibc/ipk/armv5te/
)
opkg update
opkg list
to see if the package you want is in the "available packages" list
opkg install
opkg list_installed
command
deploy/glibc/ipk/
directory once you built them with bitbake
.
You can install .ipk
packages from all mass-storage support you can connect to a board.
|
|||||||||||||||
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microchip and others, are registered trademarks or trademarks of Microchip Technology Inc. and its subsidiaries.
Arm® and others are registered trademarks or trademarks of Arm Limited (or its affiliates). Other terms and product names may be trademarks of others.
Ideas, requests, contributions ? Connect to LinksToCommunities page.