TQ product page TQMa335x

• PTXdist Linux BSP Documentation
  
• QNX® Neutrino®
  
• Windows Embedded Compact 2013

• MBa335x DIP switch settings

Preliminary fearure list

2018/05/18 -REV 0119

2017/07/07 -REV 0117

2016/04/18 - REV 0115

2014/09/22 - REV 0102

The BSP was developed for the starterkit . To use it in a product with special needs or a different basebord we suggest to define an own platform. To start with it make a copy of the platform definition and select the new platform definition

$ cd <BSPROOT>
$ cp -r <BSPROOT>/configs/platform-tq-@mb_name_code@ to <BSPROOT>/configs/<your-cool-platform>
$ ptxdist platform <BSPROOT>/configs/<your-cool-platform>/platformconfig

To start configuring your new platform type

$ ptxdist platformconfig

The first thing to change should be the platform name. Adapt things like kernel configuration, image creation etc. to your needs.

The new system will be built under <BSPROOT>/platform-<platformname_from_platformconfig>

PTXdist uses release tar balls for software it loads from the net. You have to work with patches, if you need to make changes to the source code. Follow the instructions of the developers section in the PTXdist manual.

PTXdist needs a package for every bit you need in your root FS to guarantee reproducible builds. To add your software, files etc. you have to provide local packages. Follow the instructions of the developers section in the PTXdist manual. PTXdist provides templates as starting point for own packages. Type

$ ptxdist newpackage

to see what package templates exist.

To update bootloader / kernel in a running system you have to copy the images in your tftp directory and download them to the eMMC.

To install a new firmware use SD cards. To copy the built images on the host system to a connected card type:

$ cd <BSP project>/platform-<platform_name>/images
$ sudo dd if=@mod_name_code@_hd.img of=/dev/sdf bs=1M conv=fsync #Assuming the SD card is assigned to /dev/sdf

To find out what device file the SD card has, type “dmesg” after you connect the card to see the system messages. At the bottom you'll see some “Attached scsi …” messages along with something like:

[ 8197.588395]  sdf: sdf1

See dip_switches for selecting the boot medium on the @mb_name@.

Current U-Boot versions provide a script that copies the MBR and partition contents from the SD card to the eMMC. This script is called via “run install_firmware” command at the U-Boot prompt. Due to memory limitations the root partition must be copied in a loop, each run copies the maximum memory amount available. To tell the script the size of your rootfs partition you have to use the rootblks16 variable.

This variable holds the hexadecimal number of 512-byte blocks your rootfs partition has in size.

setenv rootblks16 0x40000 

This sets a 128MB partition.

1. Boot from eMMC
2. Plug in card, power on device and stop autoboot
3. To update U-Boot type:
   run upd_uboot_sd
4. To update device tree type:
   run upd_fdt_sd
5. To update Kernel type:
   run upd_kernel_sd

1. Boot from eMMC and stop autoboot
2. Connect device via ethernet to a tftp server supplying the image
3. Provide the correct network configuration:
   setenv serverip 0.0.0.0
   setenv netmask 255.255.255.0
   setenv ipaddr 0.0.0.0
4. Provide U-Boot the file name of the desired image on the server:
   For U-Boot: setenv uboot filename
   For device tree: setenv dtb filename
   For Kernel: setenv kernel filename
5. Perform Update:
   For U-Boot: run upd_uboot_net
   For device tree: run upd_fdt_net
   For Kernel: run upd_kernel_net

To boot the @mod_name@ from network you need a working bootloader in eMMC or SD-card which is able to get the kernel image over tftp and to provide the kernel with commandline settigns for NFS. You have to provide the images via tftp and nfs and to configure the bootloader (cf. U-Boot variables boot_nfs, addnfs, kernel, dtb, serverip, rootpath) to work with your tftp-server and your nfs-server.

Finally, you will find the built images in platform-<platformname>/images.

PTXdist downloads some packages. If it reports some errors please

• verify your internet connection or proxy settings.
• make sure the package source is correct. Some package source pages will change from time to time.
  (You can always try to download the source package manually and copy it to your package pool (by default: <BSP project>\src))
• some packages like bootloaders and kernels where you can select versions need to know about their hash sums. You have to calculate them using md5sum and enter the correct hash in the ptxdist configuration.
• run

  $ ptxdist get

To configure the system use the PTXdist menu:

$ ptxdist menuconfig    →   configure the project filesystem
$ ptxdist kernelconfig  →   configure the kernel
$ ptxdist platform      →   configure the platform

Copy the gzipped SD-Card image to the rootfs of the SD-Card:

gzip sd.hdimg
cp sd.hdimg.gz $SD_MOUNT

On the target:

dd if=sd.hdimg | gunzip | dd of=/dev/mmcblk1

Alternative: copy the running image from SD-Card to the MMC:

dd if=/dev/mmcblk0 of=/dev/mmcblk1 bs=1M count=400

Change the DIP-Switches to boot from eMMC.

Hit any key to stop autoboot:  0
U-Boot# mmc dev 1
mmc1(part 0) is current device
U-Boot# set bootpart 1:1
U-Boot# run loaduimage
reading /uImage
3102000 bytes read in 351 ms (8.4 MiB/s)
U-Boot# run mmcboot
Booting from mmc ...

Boot-Order: eMMC, SD

Boot-Order: SD, SPI-NOR

Boot-Order: SPI-NOR, eMMC

to configure the TI Kernel use the following command

ptxdist menuconfig kernel-ti

1. Customise kernel respectively devicetree
2. ptxdist drop kernel-ti compile
3. ptxdist drop u-boot install
4. ptxdist images –git

There are two RTC's on the TQMa335x:

• rtc0 = RTC Sitara AM335x
• rtc1 = RTC Module PMIC

hwclock -w hwclock -f /dev/rtc0 -w

hwclock -f /dev/rtc0 --show

hwclock -w hwclock -f /dev/rtc1 -w

hwclock -f /dev/rtc1 --show

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

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

U-Boot# run loadfdt

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

U-Boot# fdt addr $fdtaddr

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:

U-Boot# fdt resize 

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

Example

U-Boot# fdt list /leds
leds {
        compatible = "gpio-leds";
        lvds_shtdn {
        };
        backlight {
        };
};
U-Boot# fdt print /leds
leds {
        compatible = "gpio-leds";
        lvds_shtdn {
                gpios = <0x0000003a 0x00000003 0x00000002>;
                default-state = "on";
        };
        backlight {
                gpios = <0x0000003a 0x00000004 0x00000002>;
                default-state = "on";
        };
};

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

U-Boot# fdt set <path> <property> <value> 

Example

U-Boot# fdt set /leds/backlight default-state off 

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

U-Boot# fatwrite mmc $bootpart $fdtaddr $fdtfile <totalsize> 

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.

Preliminary fearure list

2018/05/18 -REV 0119

2017/07/07 -REV 0117

2016/04/18 - REV 0115

2014/09/22 - REV 0102