Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:arm:tqma53:linux:how_to [2013/07/05 17:16] – [How-to] niebelen:arm:tqma53:linux:ptxdist:how_to [2022/08/04 15:02] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ~~NOCACHE~~ ~~NOCACHE~~
 +<embed en:templates:tabs_ptxdist_bootstrap>
 +  <label lang>en</label>
 +  <label mod_name>tqma53</label>
 +  <label mod_name_head>TQMa53</label>
 +  <label mod_arch>arm</label>
 +  <label bsp_name>Linux</label>
 +  <label bsp_name_head>Linux</label>
 +  <label build_system>ptxdist</label>
 +  <label build_system_head>PTXdist</label>
 +  <label product_type>Embedded module</label>
 +</embed>
 +\\
 +\\
 ====== How-to ====== ====== How-to ======
  
Line 16: Line 29:
 the names that the bootloader environment expects.   the names that the bootloader environment expects.  
    
-<note tip> To see the names needed type  +<WRAP round tip> To see the names needed type  
 <code bash>  <code bash> 
 $ cat /env/config   $ cat /env/config  
 </code>  </code> 
 at the bootloader prompt.  at the bootloader prompt. 
-</note>  +</WRAP>  
      
 You can use the update scripts from the barebox environment for update: You can use the update scripts from the barebox environment for update:
Line 47: Line 60:
  
 To update parts of the uboot environment or the device tree during development you can use also the uboot tftp command.  To update parts of the uboot environment or the device tree during development you can use also the uboot tftp command.
 +\\ 
 +\\ 
 +\\
 ===== Using different boot media ===== ===== Using different boot media =====
  
Line 76: Line 91:
  
 <code sh> <code sh>
 +barebox@TQ tqma53: saveenv
 barebox@TQ tqma53: reset barebox@TQ tqma53: reset
 </code> </code>
Line 98: Line 114:
   * Use [[.build_system#sd-card|SD-card]] boot   * Use [[.build_system#sd-card|SD-card]] boot
   * on your development host add an additional ext3 partition to the SD card   * on your development host add an additional ext3 partition to the SD card
-  * copy the hd_emmc.img file to this partition+  * copy the uboot_hd.img file to this partition
   * insert the SD card in MBa53 and boot   * insert the SD card in MBa53 and boot
   * copy the image to the eMMC using the following commands:       * copy the image to the eMMC using the following commands:    
Line 104: Line 120:
   root@tqm:~ mount /dev/mmcblk0p4 /mnt   root@tqm:~ mount /dev/mmcblk0p4 /mnt
   root@tqm:~ cd /mnt   root@tqm:~ cd /mnt
-  root@tqm:/mnt dd if=hd_emmc.img of=/dev/mmcblk1 bs=1M conv=fsync+  root@tqm:/mnt dd if=uboot_hd.img of=/dev/mmcblk1 bs=1M conv=fsync
   root@tqm:/mnt poweroff   root@tqm:/mnt poweroff
  
Line 112: Line 128:
 You can also establish an workflow using the Freescale Manufacturing tool. You can also establish an workflow using the Freescale Manufacturing tool.
  
-To boot the MBa53 from an initialized eMMC you have to set the switches S1, S2 and S3. +To boot the MBa53 from an initialized eMMC you have to set the switches S1, S2 and S3. Therfor please have a look at [[en:arm:tqma53:mba53:dip_switches#Boot Device Selection (S2 & S3)|MBa53 DIP switch settings]].
- +
-^  Switch S1 settings ^^^ +
-^ DIP ^  OFF  ^  ON  ^ +
-S2   |     | +
-| S2 2 |  X  |     | +
- +
-^  Switch S2 settings ^^^ +
-DIP ^  OFF  ^  ON  ^ +
-| S2 1 |  X  |     | +
-| S2 2 |  X  |     | +
-| S2 3 |  X  |     | +
-| S2 4 |  X  |     | +
-| S2 5 |  X  |     | +
-| S2 6 |      X  | +
-| S2 7 |      X  | +
-| S2 8 |  X  |     | +
- +
-^  Switch S3 settings ^^^ +
-^ DIP ^  OFF  ^  ON  ^ +
-| S3 1 |  X  |     | +
-| S3 2 |  X  |     | +
-| S3 3 |      X  | +
-| S3 4 |  X  |     | +
-| S3 5 |      X  | +
-| S3 6 |  X  |     | +
-| S3 7 |  X  |     | +
-| S3 8 |  X  |     |+
  
 Power up the MBa53. The login is root without any password. Power up the MBa53. The login is root without any password.
Line 152: Line 141:
 </code> </code>
  
-<note tip>You have to use the raw device of the SD card not a partition!</note>+<WRAP round tip>You have to use the raw device of the SD card not a partition!</WRAP>
  
-To boot the MBa53 from a previously generated SD Card you have to set the switches S1, S2 and S3. +To boot the MBa53 from a previously generated SD Card you have to set the switches S1, S2 and S3. Therfor please have a look at [[en:arm:tqma53:mba53:dip_switches#Boot Device Selection (S2 & S3)|MBa53 DIP switch settings]].
- +
-^  Switch S1 settings ^^^ +
-^ DIP ^  OFF  ^  ON  ^ +
-S2   |     | +
-| S2 2 |  X  |     | +
- +
-^  Switch S2 settings ^^^ +
-DIP ^  OFF  ^  ON  ^ +
-| S2 1 |  X  |     | +
-| S2 2 |  X  |     | +
-| S2 3 |  X  |     | +
-| S2 4 |  X  |     | +
-| S2 5 |  X  |     | +
-| S2 6 |      X  | +
-| S2 7 |  X  |     | +
-| S2 8 |  X  |     | +
- +
-^  Switch S3 settings ^^^ +
-^ DIP ^  OFF  ^  ON  ^ +
-| S3 1 |  X  |     | +
-| S3 2 |  X  |     | +
-| S3 3 |  X  |     | +
-| S3 4 |      X  | +
-| S3 5 |  X  |     | +
-| S3 6 |      X  | +
-| S3 7 |  X  |     | +
-| S3 8 |  X  |     |+
  
 Insert the SDcard in X6 and power up the MBa53. The login is root without any password. Insert the SDcard in X6 and power up the MBa53. The login is root without any password.
 If you connect a DVI monitor to X5 you can see the login prompt. If you connect a DVI monitor to X5 you can see the login prompt.
 +\\ 
 +\\ 
 +\\
  
 ===== Use the GPU of i.MX53 ===== ===== Use the GPU of i.MX53 =====
Line 193: Line 157:
 **For BSP rev. 0104** **For BSP rev. 0104**
  
-Follow the instructions under [[en:arm:tqma53:linux:build_system#configuration | Configuration]] and select "amd gpu binaries" entry.+Follow the instructions under [[en:arm:tqma53:linux:ptxdist:build_system#configuration| Configuration]] and select "amd gpu binaries" entry.
  
 **For BSP rev. 0105** **For BSP rev. 0105**
Line 226: Line 190:
   * sample binaries   * sample binaries
   * shared libraries   * shared libraries
 +\\ 
 +\\ 
 +\\
 ===== Adapting barebox environment ===== ===== Adapting barebox environment =====
  
Line 246: Line 212:
  
 Extending and / or overwriting the barebox default environment is also possible. Please refer the Barebox and ptxdist documentation. Extending and / or overwriting the barebox default environment is also possible. Please refer the Barebox and ptxdist documentation.
 +\\ 
 +\\ 
 +\\
 ===== Change device tree ===== ===== Change device tree =====
  
 The hardware is configured using device tree. The device tree file for TQMa53 / MBa53 is located in //platform-MBa53/build-target/linux-3.5/arch/arm/boot/dts/imx53-<MB|mb>a53.dts// after the prepare step of the kernel package. The hardware is configured using device tree. The device tree file for TQMa53 / MBa53 is located in //platform-MBa53/build-target/linux-3.5/arch/arm/boot/dts/imx53-<MB|mb>a53.dts// after the prepare step of the kernel package.
  
-<note important>**Attention:** Changes in the build directory are not saved. You need to create a patch to make the changes permanent.</note>+<WRAP round important>**Attention:** Changes in the build directory are not saved. You need to create a patch to make the changes permanent.</WRAP>
  
-<note important>**Attention:** Changes of the device tree must be compiled. To do this enter the following commands:</note>+<WRAP round important>**Attention:** Changes of the device tree must be compiled. To do this enter the following commands:</WRAP>
  
 <code sh> <code sh>
Line 284: Line 252:
 TQMa53[MBa53] > run update_dtb TQMa53[MBa53] > run update_dtb
 </code> </code>
 +\\ 
 +\\ 
 +\\
 ===== Configure USB OTG support ===== ===== Configure USB OTG support =====
  
Line 290: Line 260:
  
 //<linux-src>/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt// //<linux-src>/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt//
 +\\ 
 +\\ 
 +\\
 ===== Change display type ===== ===== Change display type =====
  
Line 297: Line 269:
 ** BSP rev 0105:** Samples for device tree are in the BSP under {BSPROOT}/local_src/dts-tqma53-3.9 ** BSP rev 0105:** Samples for device tree are in the BSP under {BSPROOT}/local_src/dts-tqma53-3.9
  
-see [[en:arm:tqma53:linux:how_to#change_device_tree|here]] how to change device tree.+see [[en:arm:tqma53:linux:ptxdist:how_to#change_device_tree|here]] how to change device tree.
  
 ==== Configure DVI / parallel display ==== ==== Configure DVI / parallel display ====
Line 451: Line 423:
    };    };
 </code> </code>
 +\\ 
 +\\ 
 +\\
  
 ===== Use Audio port ===== ===== Use Audio port =====
Line 457: Line 431:
 **TQMa53 Hardware rev. 0300** **TQMa53 Hardware rev. 0300**
  
-Works out of the Box with BSP 0105. Support for older BSP on Request.+Works out of the Box with BSP Revision ≥ 0105. Support for older BSP on Request.\\ 
 +Please have a look at our **[[intern:general_information:tutorial:audio|audio tutorial]]**, too. 
  
 **TQMa53 Hardware rev. 0200** **TQMa53 Hardware rev. 0200**
Line 467: Line 443:
  
 Change device tree following [[.:how_to#change_device_tree | these instructions]] to use audio output. Change device tree following [[.:how_to#change_device_tree | these instructions]] to use audio output.
 +\\ 
 +\\ 
 +\\
 ===== Use the VPU of i.MX53 ===== ===== Use the VPU of i.MX53 =====
  
-VPU / CODA driver is implemented as V4L2 device. To make the device usable a gstreamer plugin can be used. +VPU / CODA driver is implemented as V4L2 device. The device can be used with a gstreamer plugin
-To test the VPU you need a media file with H264 content (for instance a matroska container). To play the  +Using a media file with H264 content (for instance a matroska container) the VPU can be tested. The  
-following gstreamer pipeline can be used:+following gstreamer pipeline can be used for replay:
  
 <code> <code>
Line 490: Line 468:
  
  
 +\\ 
 +\\ 
 +\\
 ===== Compile kernel / bootloader outside of the BSP ===== ===== Compile kernel / bootloader outside of the BSP =====
  
-<note important>  +<WRAP round important>  
   * TQ System GmbH development and testing is done under the documented environment. Please consider to use the same environment for testing if you think there are issues.    * TQ System GmbH development and testing is done under the documented environment. Please consider to use the same environment for testing if you think there are issues. 
   * BSP consists of bootloader, kernel, root FS **and** plumbing for patching, configuration and building images.   * BSP consists of bootloader, kernel, root FS **and** plumbing for patching, configuration and building images.
-</note>+</WRAP>
  
 ==== The big picture ==== ==== The big picture ====
Line 504: Line 484:
 The series file describes the order how patches have to be applied. Please note that the patch series are against the documented versions of the bootloader or kernel. The series file describes the order how patches have to be applied. Please note that the patch series are against the documented versions of the bootloader or kernel.
  
-<note tip>If the first patch in the series is a tar.bz2 blob that means this will be a patch that raises the patchlevel from the base version to the bugfix version (for instance from linux 3.2 mainline to linux 3.2.20 stable)</note>+<WRAP round tip>If the first patch in the series is a tar.bz2 blob that means this will be a patch that raises the patchlevel from the base version to the bugfix version (for instance from linux 3.2 mainline to linux 3.2.20 stable)</WRAP>
  
 ==== Configuration ==== ==== Configuration ====
Line 530: Line 510:
   * Build   * Build
  
 +===== u-boot =====
 +
 +==== Reset source handling ====
  
 +The i.MX53 System Reset Controller provides information about reset sources in the SRSR register. Mainline u-boot as of v2013.01 reads this register and resets information after reading to enable clean info at next boot. Decoding is done for single reset sources only. If your baseboard contains an supervisor which is connected to the reset input of the i.MX53 two reset sources (POR and IPP USER) are detected but not decoded - the reset source is reportes an "unknown".
  • Last modified: 2022/08/04 15:04