![]() To update the default pin mux configuration with your changes just overwrite the board/dave/naon/pinmux.h file inside the U-Boot source tree with the generated one. This is the file that need to be updated in U-Boot source code ![]() pinmux.h: which contains pin mux register values for each pin.This file does NOT change when user changes pin mux configuration. mux.h: which contains only pin mux registers offset.Pix Mux Utility export function, generate two source file: rebuild u-boot and update it on your Naon boardĮxporting generated source file.export the generated source code into the U-Boot source tree.load the Naon default configuration provided by DAVE Embedded Systems.Please take a look, for example, at Additional UART on Linux (Naon) article for a step-by-step guide in how to change pin mux configuration and how to fix conflicts.Īn example of Pin Mux Utility with mux conflic Pin Mux Configuration in u-boot ĭue the fact the correct configuration of pin mux usually should be applied as soon as possible and that's better if pin mux is done is only one place, DAVE Embedded Systems choose to move all its initialization inside the startup code of U-BootĬhanging default pin mux configuration is just a matter of: the same pin configured for two function) and does not allow to export the source code when this kind of problems arise. ![]() Pin Mux Utility also warn the user if there's a conflict in mux usage (e.g. Software installation and generic usage documentation is available on this TI wiki page Pin Mux is quite complex in Naon and, fortunately, a tool from TI can help: we suggest to download and install TI Pin Mux Utility from TI website. This file will need to be placed in the first partition of the bootable SD card.The first thing to do when adding/modifying a peripheral is configure correctly the internal Pin Mux: in fact, nearly every peripheral function can be attached to more than one pin and nearly every pin is shared between two or more peripheral. Now that we have a compiler that will correctly compile U-Boot, we will configure and compile the source. So we will download version 6.4 of the gcc compiler to build U-Boot cd Unfortunately, the source in this tag does not compile with the 7.x version of the gcc compiler. We are going to use the following tag: git checkout rel_socfpga_v2013.01.01_18.06.02_pr Compiling U-BOOT We can look at the released BSPs by using the following command: git tag -l rel_socfpga* ![]() Once inside the u-boot-socfpga directory, we need to check out a recent BSP release. We can grab a copy of the Intel U-Boot source from GitHub. Instead, we are simply going to download U-Boot from the public Intel GIT repository and compile the source code into a U-Boot image. Downloading U-Bootįor the purposes of our class, we will not delve into the specifics of what U-Boot does or how to develop a board support package (BSP) for the Intel SoC. U-Boot is responsible for initializing enough of the hardware so that the Linux kernel can be loaded into memory and begin its boot process. ![]() As important as all of these tasks may be, the primary job of U-Boot is preparing the hardware to boot into Linux. These tests can include detecting devices on the PCIe bus, memory tests, and initializing board specific data. U-Boot is commonly used to run diagnostic tests on an embedded system. U-Boot is the ubiquitous boot loader for most non-x86 based CPUs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |