Table of Contents

— Template tabs_new not found.



How-To



BSP Rev.0106 add second QSPI NOR chip

In BSP Rev.0106 the second QSPI NOR chip has been removed from the default BSP configuration.
If a second device is placed on the TQMLS102xA module please apply the following changes in the
devicetree source file ls1021a-tqmls1021a.dtsi. 

 &qspi {
+       fsl,qspi-has-second-chip;
        status = "okay";
 
        qflash0: mt25ql512@0 {
@@ -139,12 +138,4 @@
                        };
                };
        };

+       qflash1: mt25ql512@1 {
+               compatible = "micron,n25q512ax3", "cfi-flash";
+               #address-cells = <1>;
+               #size-cells = <1>;
+               spi-max-frequency = <20000000>;
+               reg = <1>;
+       };
 };

Change RCW configuration

1. RCW in Taschenrechner kopieren

Use BSP Rev.0100 on MBLS102xA Rev.01xx

BSP Rev.0100 was designed to be run on Rev.0200 of the MBLS012xA.

On Rev.0200 of the MBLS102xA a different package type of the ethernet PHY is used than on Rev.01xx.
This results in different PHY addresses:

Connector Controller MBLS102xA Rev.01xx MBLS102xA Rev.02xx
X12 EC1 0x0D 0x0C
X13 EC2 0x13 0x03
X11 EC3 0x05 0x04

In order to use BSP Rev.0100 on MBLS102xA Rev.01xx the following patches must not be applied:

  • U-Boot
    • 0010-tqmls102xa-set-phy-addresses-for-mbls1021a.0200.patch
    • 0011-phy_ti-adapt-hard-coded-skew-to-custom-values.patch
  • Linux
    • 0110-arm-dt-mbls102xa-set-phy-addresses-for-rev.0200.patch
    • 0111-dt-mbls102xa-adapt-phy-timing-to-rev0200.patch

To “disable” these patches, simply comment them out in the corresponding series file:

  • U-Boot: configs/platform-tq-mbls102xa/patches/u-boot-2016.05/series
  • Linux: configs/platform-tq-mbls102xa/patches/linux-4.4/series

Please note that the following interfaces cannot be used when using Rev.01xx of the MBLS102xA:

  • EC2
  • SATA


Use BSP Rev.0100 on MBLS102xA Rev.01xx

BSP Rev.0100 was designed to be run on Rev.0200 of the MBLS012xA.

On Rev.0200 of the MBLS102xA a different package type of the ethernet PHY is used than on Rev.01xx.
This results in different PHY addresses:

Connector Controller MBLS102xA Rev.01xx MBLS102xA Rev.02xx
X12 EC1 0x0D 0x0C
X13 EC2 0x13 0x03
X11 EC3 0x05 0x04

In order to use BSP Rev.0100 on MBLS102xA Rev.01xx the following patches must not be applied:

  • U-Boot
    • 0010-tqmls102xa-set-phy-addresses-for-mbls1021a.0200.patch
    • 0011-phy_ti-adapt-hard-coded-skew-to-custom-values.patch
  • Linux
    • 0110-arm-dt-mbls102xa-set-phy-addresses-for-rev.0200.patch
    • 0111-dt-mbls102xa-adapt-phy-timing-to-rev0200.patch

To “disable” these patches, simply comment them out in the corresponding series file:

  • U-Boot: configs/platform-tq-mbls102xa/patches/u-boot-2016.05/series
  • Linux: configs/platform-tq-mbls102xa/patches/linux-4.4/series



Load / Change / Save the Device Tree under U-Boot


Devicetree can be edit with the fdt commands under U-Boot.

For testing purpose only. For bigger changes, please compile the Devicetree.
Therefore you can have a look at the following tutorial.
Tested with TQMLS102xA BSP Rev.0102

1) At first the fdt file has to be loaded from the current boot medium (mmc) into RAM. 

=> run loadfdt

2) Next step is to set the predefined U-Boot environment variable fdt_addr through the fdt addr command. 

=> fdt addr $fdt_addr

3) Afterwards the size of the fdt has to be increased (to the next 4K divider) in order to have some space for modifications. This is simply done by entering: 

=> fdt resize

4) List device in the tree you want to change to have a look at the default settings.

Example

5) To modify a value of a propertie use the fdt set command. 

=> fdt set <path> <property> <value>

Example

6) Optional: If you want to save your modified Devicetree back to mmc you'll have to run the following command: 

=> mmc dev $mmcdev; mmc write $fdt_addr $fdt_start $fdt_size

* BSP Rev. >0102 <code>⇒ fatwrite mmc $mmcdev:$firmwarepart $fdt_addr $fdt_file <totalsize></code> You can find out <totalsize> of the modified fdt by entering the command fdt header Otherwise you can boot your module with the changed Devicetree right after the modification.