summaryrefslogtreecommitdiff
path: root/nuttx/configs/pic32-starterkit/README.txt
diff options
context:
space:
mode:
Diffstat (limited to 'nuttx/configs/pic32-starterkit/README.txt')
-rw-r--r--nuttx/configs/pic32-starterkit/README.txt24
1 files changed, 10 insertions, 14 deletions
diff --git a/nuttx/configs/pic32-starterkit/README.txt b/nuttx/configs/pic32-starterkit/README.txt
index d9a562fe1..e2c625419 100644
--- a/nuttx/configs/pic32-starterkit/README.txt
+++ b/nuttx/configs/pic32-starterkit/README.txt
@@ -469,40 +469,36 @@ Creating Compatible NuttX HEX files
directory:
1) nuttx - This is an ELF file, and
- 2) nuttx.ihx - This is an Intel Hex format file. This is controlled by
+ 2) nuttx.hex - This is an Intel Hex format file. This is controlled by
the setting CONFIG_INTELHEX_BINARY in the .config file.
- However, there are two problems with the generated nutt.ihx:
-
- 1) The tool expects Intel Hex format files to be named *.hex. This
- is not a significant issue. However, just renaming the file to
- nuttx.hex is *not* sufficient. There is another problem:
- 2) The tool expects the nuttx.hex file to contain physical addresses.
- But the nuttx.ihx file generated from the top-level make will have
- address in the KSEG0 and KSEG1 regions.
+ The PICkit tool wants an Intel Hex format file to burn into FLASH. However,
+ there is a problem with the generated nutt.hex: The tool expects the nuttx.hex
+ file to contain physical addresses. But the nuttx.hex file generated from the
+ top-level make will have address in the KSEG0 and KSEG1 regions.
tools/mkpichex:
---------------
There is a simple tool in the configs/pic32-starterkit/tools directory
- that can be used to solve both issues with the nuttx.ihx file. But,
+ that can be used to solve both issues with the nuttx.hex file. But,
first, you must build the the tools:
cd configs/pic32-starterkit/tools
make
Now you will have an excecutable file call mkpichex (or mkpichex.exe on
- Cygwin). This program will take the nutt.ihx file as an input, it will
+ Cygwin). This program will take the nutt.hex file as an input, it will
convert all of the KSEG0 and KSEG1 addresses to physical address, and
- it will write the modified file as nuttx.hex.
+ it will write the modified file, replacing the original nuttx.hex.
To use this file, you need to do the following things:
. ./setenv.sh # Source setenv.sh. Among other this, this script
# will add configs/pic32-starterkit/tools to your
# PATH variable
- make # Build nuttx and nuttx.ihx
- mkpichex $PWD # Convert nuttx.ihx to nuttx.hex. $PWD is the path
+ make # Build nuttx and nuttx.hex
+ mkpichex $PWD # Convert addresses in nuttx.hex. $PWD is the path
# to the top-level build directory. It is the only
# required input to mkpichex.