After Building the BSP three bin files will be created in images directory. All these vectors must be B-branch or LDR load register instructions except for the sixth vector. This vector is used to store the size of the image to download. If a valid sequence is found, code is downloaded into the internal SRAM.
|Published (Last):||16 April 2019|
|PDF File Size:||4.20 Mb|
|ePub File Size:||2.66 Mb|
|Price:||Free* [*Free Regsitration Required]|
Thus no specific programming hardware is required to program the final application into the on-chip flash memory. On Linux, simply enter nutconf on the shell prompt. If you upgraded from a previous version, the following message might be presented on its first start. You may chose Yes and let the Configurator adapt the new installation path or select No and correct the path later.
The Configurator typically starts with a file selection dialog, from which you can choose a pre-configuration for a specific board. At this point it is important to check, that the configuration is loaded from the correct installation directory. Check the log window to make sure, that the repository and the configuration file had been loaded from the current installation directory.
If not correct, you may reload the configuration later. For now, just continue. First some Configurator settings need to be specified. These settings are stored in the Windows repository. A tabbed dialog with four pages appears. On the first page, titled Repository you can specify the path of the repository file. You do not need to know anything about it unless you want to implement new drivers etc.
Remember the log in the main window? If the wrong repository had been loaded, you can correct this here. Always use Unix like slashes to separate directory paths, not Windows like backslashes.
It is recommended to stick with the defaults shown. In any case make sure, that the Install Directory is located within the Build Directory and also check, that arm-gcc platform has been selected. On the third page the build environment has to be specified. In contrary to the rule stated above, backslashes can be used here.
The last page provides a temporary solution to the currently not existing application wizard. The programmer selection can be ignored. Click OK to confirm all settings and return to the main window. This way the correct repository will be loaded. In a first step the build directory will be prepared. Check the displayed paths again and click OK. Click OK to start this build. It may take some time to finish. Check the output in the log window.
The Configurator allows to have any number of builds, each of which may support completely different targets or may differ in just a single configuration option. Each build may have one or more associated application directories. The easiest way to create such a directory is to let the Configurator create one. If you already created this directory before and modified any of the samples, your changes will get lost.
If unsure, click Abort and specify another application directory in the Configurator settings. Otherwise click OK. Finally terminate the Configurator. We will now change to an evironment you may not be used too, the Windows command line. Open a command line window, for example by executing cmd. Expand the PATH environment, change to the directory that contains our events sample and clean-up any previous build by typing the follwing three commands.
As a final result, two files will be created, which contain the binary code of our sample application. One is in Intel hex format events. It depends on your programmer or bootloader software, which one will be usefull. Creating this directory manually will fix this problem. Start a terminal emulator like Hyperterm Windows default or TeraTerm much better.
Serial port settings are ,8,n,1. Double click on the file events. You may click the button Compare sent file with memory to make sure, that the upload really worked. In order to start the uploaded code, enter go 0x in the script window. Good luck,.
Subscribe to RSS
ATMEL AT91SAM9260 ARM SOM
Atmel ARM-based processors
Nut/OS on the AT91SAM9260 EK