Difference between revisions of "Sources organisation"
From ArmadeusWiki
m |
|||
| Line 10: | Line 10: | ||
| |-- project | | |-- project | ||
| |-- project_build_arm | | |-- project_build_arm | ||
| + | | | `--armadeus | ||
| |-- scripts | | |-- scripts | ||
| |-- target | | |-- target | ||
| Line 44: | Line 45: | ||
`-- test | `-- test | ||
| − | ==binaries folder== | + | ==binaries/armadeus folder== |
Contains the generated binary files | Contains the generated binary files | ||
| − | * linux-2.6.xxx.bin | + | * linux-kernel-2.6.xxx-arm.bin |
| − | * rootfs.jffs2 | + | * rootfs.arm.jffs2 |
* uboot.bin | * uboot.bin | ||
==build_arm folder== | ==build_arm folder== | ||
| + | This place is used to compile the softwares which will run on your target like linux, u-boot...<br> | ||
| + | A new package selected in the buildroot menuconfig will have a dedicated directory here.<br> | ||
| + | Modifications of the target software have to be done here during the development phase. <br> | ||
| + | The arm compiler for your platform and the libs are although placed here (under staging_dir) | ||
| − | ==project_build_arm folder== | + | == package folder == |
| + | This place contains all the packages available from the buildroot menuconfig.<br> | ||
| + | Each package has its own folder with a makefile and several patches if required.<br> | ||
| + | The makefile is responsible for the download of the software and for the installation in the build_arm folder.<br> | ||
| + | *If you need to change the version of a package, you have to do the modification in the makefile. | ||
| + | |||
| + | ==project_build_arm/armadeus folder== | ||
| + | === root === | ||
This place is used to build the whole rootfs for your board. <br> | This place is used to build the whole rootfs for your board. <br> | ||
*If you need to modify your rootfs (ie add nodes, startup files), you can do the modifications here during the development phase.<br> | *If you need to modify your rootfs (ie add nodes, startup files), you can do the modifications here during the development phase.<br> | ||
| Line 60: | Line 72: | ||
The rootfs can be clean up with the following command: | The rootfs can be clean up with the following command: | ||
$ make roofs-dirclean (in the top Armadeus directory) | $ make roofs-dirclean (in the top Armadeus directory) | ||
| + | |||
| + | === busybox-xxxx === | ||
| + | This directory used to compile the busybox for your target. | ||
| + | *the configuration of your busybox can be changed like that: | ||
| + | $ make busybox-menuconfig (in the top Armadeus directory) | ||
| + | |||
==target/device/armadeus folder== | ==target/device/armadeus folder== | ||
Revision as of 23:04, 19 April 2008
Contents
Project Tree
|-- buildroot ---------------------- contains our buildroot distribution | |-- binaries | | `-- armadeus------------------ contains image files for the target: u-boot, kernel, rootfs | |-- build_arm | |-- docs | |-- package | |-- project | |-- project_build_arm | | `--armadeus | |-- scripts | |-- target | | `-- device | | `-- armadeus | | |-- apf9328 | | |-- apm9328 | | |-- linux | | | `-- kernel-patches | | |-- rootfs | | | `-- target_skeleton | | `-- u-boot | |-- toolchain | `-- toolchain_build_arm |-- downloads ---------------------- holds all the downloaded files by default |-- firmware ----------------------- contains the custom FPGA's IPs | |-- BRAMTest | |-- led | |-- PS2 | |-- PS2_Opencore | `-- sram_test |-- host -------------------------- contains the custom software needed on the devt PC | `-- patches |-- patches ----------------------- contains the patches needed to be applied to buildroot | `-- cygwin |-- software ---------------------- contains software running one part on the PC and one part on the APF | |-- demos | |-- orchesta | `-- uboot_recover `-- target ------------------------ contains all our custom software for the APF |-- demos |-- linux |-- packages `-- test
binaries/armadeus folder
Contains the generated binary files
- linux-kernel-2.6.xxx-arm.bin
- rootfs.arm.jffs2
- uboot.bin
build_arm folder
This place is used to compile the softwares which will run on your target like linux, u-boot...
A new package selected in the buildroot menuconfig will have a dedicated directory here.
Modifications of the target software have to be done here during the development phase.
The arm compiler for your platform and the libs are although placed here (under staging_dir)
package folder
This place contains all the packages available from the buildroot menuconfig.
Each package has its own folder with a makefile and several patches if required.
The makefile is responsible for the download of the software and for the installation in the build_arm folder.
- If you need to change the version of a package, you have to do the modification in the makefile.
project_build_arm/armadeus folder
root
This place is used to build the whole rootfs for your board.
- If you need to modify your rootfs (ie add nodes, startup files), you can do the modifications here during the development phase.
This folder is created during the first toolchain installation. A rootfs skeleton located in target/device/armadeus/roofs is used to build the initial rootfs.
- If you want to keep a special rootfs across projects, the skeleton has to be replaced with your own file.
The rootfs can be clean up with the following command:
$ make roofs-dirclean (in the top Armadeus directory)
busybox-xxxx
This directory used to compile the busybox for your target.
- the configuration of your busybox can be changed like that:
$ make busybox-menuconfig (in the top Armadeus directory)
