Changeset f028448 in rtems-docs
- Timestamp:
- 08/03/22 04:20:52 (17 months ago)
- Branches:
- master
- Children:
- 3859073
- Parents:
- e551cc7
- git-author:
- Chris Johns <chrisj@…> (08/03/22 04:20:52)
- git-committer:
- Chris Johns <chrisj@…> (08/03/22 04:28:19)
- Location:
- user/bsps
- Files:
-
- 7 edited
Legend:
- Unmodified
- Added
- Removed
-
user/bsps/arm/altera-cyclone-v.rst
re551cc7 rf028448 28 28 .. code-block:: none 29 29 30 arm-rtems 5-objcopy -O binary app.exe app.bin30 arm-rtems@rtems-ver-major@-objcopy -O binary app.exe app.bin 31 31 gzip -9 -f -c app.bin > app.bin.gz 32 32 mkimage -A arm -O linux -T kernel -a 0x00300000 -e 0x00300000 -n RTEMS -d app.bin.gz app.img -
user/bsps/arm/beagle.rst
re551cc7 rf028448 33 33 .. code-block:: none 34 34 35 arm-rtems 5-objcopy hello.exe -O binary app.bin35 arm-rtems@rtems-ver-major@-objcopy hello.exe -O binary app.bin 36 36 gzip -9 app.bin 37 37 mkimage -A arm -O linux -T kernel -a 0x80000000 -e 0x80000000 -n RTEMS -d app.bin.gz rtems-app.img … … 78 78 For example, 79 79 80 .. code-block:: 80 .. code-block:: none 81 81 82 /dts-v1/; 82 83 … … 110 111 The function prototype is given below: 111 112 112 .. code-block:: C113 .. code-block:: c 113 114 114 115 rtems_status_code bsp_register_spi( … … 154 155 The resulting wiring is: 155 156 156 .. code-block:: 157 .. code-block:: none 157 158 158 159 1 === /--=== 2 … … 199 200 following gdb start script can be used: 200 201 201 .. code-block:: 202 .. code-block:: none 202 203 203 204 define reset -
user/bsps/arm/imx.rst
re551cc7 rf028448 16 16 --------------------------- 17 17 18 The following options are available at the configure command line. 18 The following options can be used in the BSP section of the waf 19 configuration INI file. The waf defaults can be used to inspect the 20 values. 19 21 20 22 ``BSP_PRESS_KEY_FOR_RESET`` … … 74 76 .. code-block:: none 75 77 76 arm-rtems 5-objcopy -O binary app.exe app.bin78 arm-rtems@rtems-ver-major@-objcopy -O binary app.exe app.bin 77 79 gzip -9 -f -c app.bin > app.bin.gz 78 80 mkimage -A arm -O linux -T kernel -a 0x80200000 -e 0x80200000 -n RTEMS -d app.bin.gz app.img -
user/bsps/arm/imxrt.rst
re551cc7 rf028448 40 40 compiled RTEMS application with for example:: 41 41 42 arm-rtems 6-objcopy -O binary build/arm/imxrt1052/testsuites/samples/hello.exe hello.bin42 arm-rtems@rtems-ver-major@-objcopy -O binary build/arm/imxrt1052/testsuites/samples/hello.exe hello.bin 43 43 44 44 Then just copy the generated binary to the mass storage provided by the … … 92 92 `bsps/arm/imxrt/dts/imxrt1050-evkb.dts`. The FDT is split up into two parts. The 93 93 core part is put into an `dtsi` file and is installed together with normal 94 headers into `${PREFIX}/arm-rtems6/imxrt1052/lib/include`. You can use that to 95 create your own device tree based on that. Basically use something like:: 94 headers into `${PREFIX}/arm-rtems@rtems-ver-major@/imxrt1052/lib/include`. You 95 can use that to create your own device tree based on that. Basically use 96 something like:: 96 97 97 98 /dts-v1/; 98 99 99 100 #include <imxrt/imxrt1050-pinfunc.h> 100 101 #include <imxrt/imxrt1050.dtsi> 101 102 102 103 &lpuart1 { 103 104 pinctrl-0 = <&pinctrl_lpuart1>; 104 105 status = "okay"; 105 106 }; 106 107 107 108 &chosen { 108 109 stdout-path = &lpuart1; 109 110 }; 110 111 111 112 /* put your further devices here */ 112 113 113 114 &iomuxc { 114 115 pinctrl_lpuart1: lpuart1grp { … … 118 119 >; 119 120 }; 120 121 121 122 /* put your further pinctrl groups here */ 122 123 }; 123 124 124 125 You can then convert your FDT into a C file with (replace `YOUR.dts` and similar 125 with your FDT source names):: 126 127 sh> arm-rtems6-cpp -P -x assembler-with-cpp \ 128 -I ${PREFIX}/arm-rtems6/imxrt1052/lib/include \ 129 -include "YOUR.dts" /dev/null | \ 130 dtc -O dtb -o "YOUR.dtb" -b 0 -p 64 126 with your FDT source names): 127 128 .. code-block:: none 129 130 sh> arm-rtems@rtems-ver-major@-cpp -P -x assembler-with-cpp \ 131 -I ${PREFIX}/arm-rtems@rtems-ver-major@/imxrt1052/lib/include \ 132 -include "YOUR.dts" /dev/null | \ 133 dtc -O dtb -o "YOUR.dtb" -b 0 -p 64 131 134 sh> rtems-bin2c -A 8 -C -N imxrt_dtb "YOUR.dtb" "YOUR.c" 132 135 … … 146 149 147 150 #include "fsl_clock_config.h" 148 151 149 152 const clock_arm_pll_config_t armPllConfig_BOARD_BootClockRUN = { 150 153 .loopDivider = 100, -
user/bsps/arm/raspberrypi.rst
re551cc7 rf028448 13 13 14 14 Setup SD card 15 ------------- ---15 ------------- 16 16 17 17 The Raspberry Pis have an unconventional booting mechanism. The GPU … … 21 21 `kernel=<img_name>` to ``config.txt``. 22 22 23 You must provide the required firmware files on the SD card for the GPU to proceed,24 and thereby to boot RTEMS. 25 The BSP currently boots up with an older version of the official firmware. These files 26 can be downloaded from 27 `the Raspberry Pi Firmware Repository <https://github.com/raspberrypi/firmware/tree/1.20200601/boot>`_. 28 You can remove the ``kernel*.img`` files if you want to, but don't touch 29 the otherfiles.23 You must provide the required firmware files on the SD card for the GPU to 24 proceed, and thereby to boot RTEMS. The BSP currently boots up with an older 25 version of the official firmware. These files can be downloaded from `the 26 Raspberry Pi Firmware Repository 27 <https://github.com/raspberrypi/firmware/tree/1.20200601/boot>`_. You can 28 remove the ``kernel*.img`` files if you want to, but don't touch the other 29 files. 30 30 31 31 Copy these files in to a SD card with FAT filesystem. … … 42 42 .. code-block:: none 43 43 44 $ arm-rtems5-objcopy -Obinary hello.exe kernel.img44 $ xsarm-rtems@rtems-ver-major@-objcopy -Obinary hello.exe kernel.img 45 45 46 46 Copy the kernel image to the SD card. … … 55 55 56 56 SPI Driver 57 ---------- --57 ---------- 58 58 59 59 SPI drivers are registered by the ``rpi_spi_init(bool bidirectional_mode)`` function. … … 73 73 74 74 I2C Driver 75 ---------- --75 ---------- 76 76 77 77 I2C drivers are registered by the ``rpi_setup_i2c_bus()`` function. … … 133 133 .. code-block:: none 134 134 135 $ arm-rtems 5-gdb hello.exe135 $ arm-rtems@rtems-ver-major@-gdb hello.exe 136 136 137 137 This will open GDB and will load the symbol table from hello.exe. Issue the -
user/bsps/arm/xen.rst
re551cc7 rf028448 43 43 .. code-block:: none 44 44 45 arm-rtems 5/c/xen_virtual/testsuites/samples/ticker.exe45 arm-rtems@rtems-ver-major@/c/xen_virtual/testsuites/samples/ticker.exe 46 46 47 47 The ``ticker.exe`` elf file must be translated to a binary format. … … 49 49 .. code-block:: none 50 50 51 arm-rtems 5-objcopy -O binary ticker.exe ticker.bin51 arm-rtems@rtems-ver-major@-objcopy -O binary ticker.exe ticker.bin 52 52 53 53 Then place the ``ticker.bin`` file on the dom0 filesystem. -
user/bsps/bsps-arm.rst
re551cc7 rf028448 7 7 ********* 8 8 9 .. include:: arm/altera-cyclone-v.rst 10 .. include:: arm/atsam.rst 11 .. include:: arm/beagle.rst 12 .. include:: arm/csb336.rst 13 .. include:: arm/csb337.rst 14 .. include:: arm/edb7312.rst 15 .. include:: arm/gumstix.rst 16 .. include:: arm/imx.rst 17 .. include:: arm/imxrt.rst 18 .. include:: arm/lm3s69xx.rst 19 .. include:: arm/lpc176x.rst 20 .. include:: arm/lpc24xx.rst 21 .. include:: arm/raspberrypi.rst 22 .. include:: arm/realview-pbx-a9.rst 23 .. include:: arm/rtl22xx.rst 24 .. include:: arm/smdk2410.rst 25 .. include:: arm/stm32f4.rst 26 .. include:: arm/stm32h7.rst 27 .. include:: arm/tms570.rst 28 .. include:: arm/xen.rst 29 .. include:: arm/xilinx-zynq.rst 30 .. include:: arm/xilinx-zynqmp.rst 9 .. toctree:: 10 11 arm/altera-cyclone-v.rst 12 arm/atsam.rst 13 arm/beagle.rst 14 arm/csb336.rst 15 arm/csb337.rst 16 arm/edb7312.rst 17 arm/gumstix.rst 18 arm/imx.rst 19 arm/imxrt.rst 20 arm/lm3s69xx.rst 21 arm/lpc176x.rst 22 arm/lpc24xx.rst 23 arm/raspberrypi.rst 24 arm/realview-pbx-a9.rst 25 arm/rtl22xx.rst 26 arm/smdk2410.rst 27 arm/stm32f4.rst 28 arm/stm32h7.rst 29 arm/tms570.rst 30 arm/xen.rst 31 arm/xilinx-zynq.rst 32 arm/xilinx-zynqmp.rst
Note: See TracChangeset
for help on using the changeset viewer.