diff options
author | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2013-03-12 16:02:48 +0000 |
---|---|---|
committer | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2013-03-12 16:02:48 +0000 |
commit | 774fdc43f3bea13b7852d82536ff96ccbb7ebf03 (patch) | |
tree | 670045481e8342d0ac70fce4c27f690133b2a883 /nuttx/configs/sam3u-ek | |
parent | d92f89d08d0729d4c7c32fd5d6d2892c4408dcb4 (diff) | |
download | px4-nuttx-774fdc43f3bea13b7852d82536ff96ccbb7ebf03.tar.gz px4-nuttx-774fdc43f3bea13b7852d82536ff96ccbb7ebf03.tar.bz2 px4-nuttx-774fdc43f3bea13b7852d82536ff96ccbb7ebf03.zip |
A few early fixes in kernel build testing
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5734 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/configs/sam3u-ek')
-rw-r--r-- | nuttx/configs/sam3u-ek/README.txt | 50 |
1 files changed, 36 insertions, 14 deletions
diff --git a/nuttx/configs/sam3u-ek/README.txt b/nuttx/configs/sam3u-ek/README.txt index c5daedbe7..e94a9a319 100644 --- a/nuttx/configs/sam3u-ek/README.txt +++ b/nuttx/configs/sam3u-ek/README.txt @@ -378,26 +378,48 @@ must be is one of the following: knsh: This is identical to the nsh configuration below except that NuttX is built as a kernel-mode, monolithic module and the user applications - are built separately. This build requires a special make command; not - just 'make' but make with the following two arguments: + are built separately. It is recommends to use a special make command; + not just 'make' but make with the following two arguments: make pass1 pass2 - This is required because in the normal case (just 'make'), make will - create all dependencies then execute the pass1 and pass2 targets. But - this example, pass2 depends on auto-generatd files produced during pass1. - This special make command ('make pass1 pass2') will make the dependencies - separately for each pass. + In the normal case (just 'make'), make will attempt to build both user- + and kernel-mode blobs more or less interleaved. This actual works! + However, for me it is very confusing so I prefer the above make command: + Make the user-space binaries first (pass1), then make the the kernel-space + binaries (pass2) - At the end of the build, there four files will top-level build - directory: + NOTES: + + 1. This configuration uses the mconf-based configuration tool. To + change this configuration using that tool, you should: + + a. Build and install the kconfig-mconf tool. See nuttx/README.txt + and misc/tools/README.txt. + + b. Execute 'make menuconfig' in nuttx/ in order to start the + reconfiguration process. + + 2. Uses the older, OABI, buildroot toolchain. But that is easily + reconfigured: + + CONFIG_ARMV7M_TOOLCHAIN_BUILDROOT=y : Buildroot toolchain + CONFIG_ARMV7M_OABI_TOOLCHAIN=y : Older, OABI toolchain + + 3. At the end of the build, there will be several files in the top-level + NuttX build directory: + + PASS1: + nuttx_user.elf - The pass1 user-space ELF file + nuttx_user.hex - The pass1 Intel HEX format file (selected in defconfig) + User.map - Symbols in the user-space ELF file - nuttx_user.elf - The pass1 ELF file - nuttx - The pass2 ELF file - nuttx_user.hex - The pass1 Intel HEX format file - nuttx.hex - The pass2 Intel HEX file + PASS2: + nuttx - The pass2 kernel-space ELF file + nuttx.hex - The pass2 Intel HEX file (selected in defconfig) + System.map - Symbols in the kernel-space ELF file - The J-Link program will except files in .hex, .mot, .srec, and .bin + The J-Link programmer will except files in .hex, .mot, .srec, and .bin formats. nsh: |