Skip to content

Latest commit

 

History

History
416 lines (264 loc) · 12.7 KB

README.md

File metadata and controls

416 lines (264 loc) · 12.7 KB

ti-am572x-idk

The whole image can be build with this

export BUILD_DEVICE=ti-am572x-idk
bitbake aws-biga-image

BE CARFUL THIS TUTORIAL IS OUTDATED, at least for the build instructions!

AWS IoT Greengrass for the Texas Instruments AM572x Industrial Development Kit

  1. Build the image.

    cd $BASEDIR/tisdk/build
. conf/setenv
bitbake -r conf/am572x_iot_greengrass.conf arago-base-tisdk-image

    After building, the images will be in the following directory.

    $BASEDIR/tisdk/build/arago-tmp-external-arm-toolchain/deploy/images/am57xx-evm

  2. Change directory and then create a boot partition archive.

    cd $BASEDIR/tisdk/build/arago-tmp-external-arm-toolchain/deploy/images/am57xx-evm
tar -chJf u-boot.tar.xz MLO u-boot.img zImage

  3. Use the TI flashing tools to flash the image. In this version of the SDK, the flashing tool is in this directory.

    cd $HOME/ti-processor-sdk-linux-am57xx-evm-06.02.00.81/bin

  4. Because the tool must access peripherals as root, we must run with the sudo command.

    sudo ./create-sdcard.sh

    Follow the instructions at SD Card Using Custom Images.

    Replace UID with your home directory's ID to complete the fully qualified paths. You will input the fully qualified path for the boot files:

    /home/UID/tisdk/build/arago-tmp-external-arm-toolchain/deploy/images/am57xx-evm/u-boot.tar.xz

    And the fully qualified path for the rootfs (your time and date will vary ):

    /home/UID/tisdk/build/arago-tmp-external-arm-toolchain/deploy/images/am57xx-evm/arago-base-tisdk-image-am57xx-evm-20200409163450.rootfs.tar.xz

  5. Unmount the microSD card from your workstation.

  6. Boot the system as normal (turn on with SW3, reset with SW2), using a 115200N81 connection speed. There has been mixed results using screen and minicom. Best results have been demonstrated on picocom on Linux and TeraTerm on Windows.

    sudo apt-get install picocom
picocom -b 115200 /dev/ttyUSB1

Go build solutions

Your image with IoT Greengrass is now up and running. What's next?

When you go through the IoT Greengrass Tutorial, know that Module 1 and Module 2 has already been mostly completed. You will need to follow the Configure AWS IoT Greengrass on AWS IoT chapter to initialize your account for IoT Greengrass, create your Greengrass Group, and then apply the config.json and credentials to the target device.

Testing with AWS IoT Device Tester (IDT)

AWS IoT Device Tester requires additional additional software. To build the image for IDT, please use the am572x_iot_greengrass_idt.conf file. You will need to install package =ntp= for use of =ntpd= or else Greengrass OTA testing will fail due to potential system time mismatch causing the SSL handshake during =wget= invocation to fail.

wget https://raw.githubusercontent.com/aws-samples/meta-aws-demos/master/am572x_idk/aws_iot_greengrass/am572x_iot_greengrass_idt.conf
mv am572x_iot_greengrass_idt.conf $BASEDIR/tisdk/build/conf/am572x_iot_greengrass_idt.conf

If you would also like to perform IDT tests for Stream Manager and Connectors (which requires Docker), use the following configuration file:

wget https://raw.githubusercontent.com/aws-samples/meta-aws-demos/master/am572x_idk/aws_iot_greengrass/am572x_iot_greengrass_idt_full.conf
mv am572x_iot_greengrass_idt.conf $BASEDIR/tisdk/build/conf/am572x_iot_greengrass_idt_full.conf

If you are building the full version, then you will need to add OpenJDK to the build. IoT Greengrass version 1.10 and later requires the Java Development Kit for Stream Manager. Clone the meta-java repository and align with the zeus branch.

cd $BASEDIR/tisdk/sources/
git clone -b zeus https://git.yoctoproject.org/git/meta-java

Add the meta-java layer to the build.

/src/tisdk/build/conf$ diff bblayers.conf.1 bblayers.conf
30a31,32
> 	/src/tisdk/sources/meta-aws \
> 	/src/tisdk/sources/meta-java \

Download and install IDT to your host system. In this walkthrough, we are using IDT v3.0.0 for Linux.

cd $HOME
unzip ~/Downloads/devicetester_greengrass_linux_3.0.1.zip

Configuration files are in directory /devicetester_greengrass_linux/configs. We have provided sample config.json and device.json files. The config.json is setup to use your CLI authentication (see Setting Configuration to Run the AWS IoT Greengrass Qualification Suite in the IoT Greengrass documentation). The device.json file is configured for the Device Under Test.

After building, perform the microSD imaging process defined in the Build and flash the image section.

After imaging, insert the microSD to the device. Boot and login to the system as root. Change the password to @w$4L1f3 using the mkpasswd command. Identify the IP address of the machine by running the ifconfig command and change device.json accordingly.

After performing the settings, ensure Greengrass is off. If you had previously installed certificates and config to the rootfs, then Greengrass might be started and will interfere with IDT results.

./devicetester_linux_x86-64 run-suite --suite-id GGQ_1.0.0 --pool-id 1

Cleaning up

If you are running locally and do not have intent to continue working on the local workstation, cleanup (with the exception of installed packages) can be done in three simple steps:

rm -rf $BASEDIR/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf
rm -rf $BASEDIR/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu
rm -rf $BASEDIR/tisdk

Notes

OpenJDK compilation problem

If you need to build on =warrior=, set openjdk-8 to be installed for the stream manager feature, and get a message that says "OS not supported" then add the following to your local.conf:

EXTRA_OEMAKE += "DISABLE_HOTSPOT_OS_VERSION_CHECK=ok"

Typical create-sdcard.sh output

$ sudo ./create-sdcard.sh
[sudo] password for me:
Authenticated with cached credentials.


################################################################################

This script will create a bootable SD card from custom or pre-built binaries.

The script must be run with root permissions and from the bin directory of
the SDK

Example:
 $ sudo ./create-sdcard.sh

Formatting can be skipped if the SD card is already formatted and
partitioned properly.

################################################################################


Available Drives to write images to:

#  major   minor    size   name
1:   8        0   31260672 sda

Enter Device Number or n to exit: 1

sda was selected

################################################################################

		**********WARNING**********

	Selected Device is greater then 16GB
	Continuing past this point will erase data from device
	Double check that this is the correct SD Card

################################################################################

Would you like to continue [y/n] : y




/dev/sda is an sdx device
Unmounting the sda drives
 unmounted /dev/sda1
 unmounted /dev/sda2
Current size of sda1 71680 bytes
Current size of sda2 31171584 bytes

################################################################################

	Select 2 partitions if only need boot and rootfs (most users).
	Select 3 partitions if need SDK & other content on SD card.  This is
        usually used by device manufacturers with access to partition tarballs.

	****WARNING**** continuing will erase all data on sda

################################################################################

Number of partitions needed [2/3] : 2


Now partitioning sda with 2 partitions...


################################################################################

		Now making 2 partitions

################################################################################

1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.119627 s, 8.8 MB/s
DISK SIZE - 32010928128 bytes

################################################################################

		Partitioning Boot

################################################################################
mkfs.fat 4.1 (2017-01-24)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows

################################################################################

		Partitioning rootfs

################################################################################
mke2fs 1.44.1 (24-Mar-2018)
/dev/sda2 contains a ext3 file system labelled 'rootfs'
	last mounted on /media/rootfs on Sat Apr 11 19:34:58 2020
Proceed anyway? (y,N) y
Creating filesystem with 7792896 4k blocks and 1949696 inodes
Filesystem UUID: 0a8ef0f2-9008-4d46-a5a0-d3be7b6ae2a2
Superblock backups stored on blocks:
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
	4096000

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done   



################################################################################

   Partitioning is now done
   Continue to install filesystem or select 'n' to safe exit

   **Warning** Continuing will erase files any files in the partitions

################################################################################


Would you like to continue? [y/n] : y



Mount the partitions

Emptying partitions


Syncing....

################################################################################

	Choose file path to install from

	1 ) Install pre-built images from SDK
	2 ) Enter in custom boot and rootfs file paths

################################################################################

Choose now [1/2] : 2



################################################################################

  For U-boot and MLO

  If files are located in Tarball write complete path including the file name.
      e.x. $:  /home/user/MyCustomTars/boot.tar.xz

  If files are located in a directory write the directory path
      e.x. $: /ti-sdk/board-support/prebuilt-images/

  NOTE: Not all platforms will have an MLO file and this file can
        be ignored for platforms that do not support an MLO.

  Update: The proper location for the kernel image and device tree
          files have moved from the boot partition to the root filesystem.

################################################################################

Enter path for Boot Partition : /home/me/tisdk/build/arago-tmp-external-arm-toolchain/deploy/images/am57xx-evm/u-boot.tar.xz

File exists



################################################################################

   For Kernel Image and Device Trees files

    What would you like to do?
     1) Reuse kernel image and device tree files found in the selected rootfs.
     2) Provide a directory that contains the kernel image and device tree files
        to be used.

################################################################################

Choose option 1 or 2 : 1


Reusing kernel and dt files from the rootfs's boot directory



################################################################################

   For Rootfs partition

   If files are located in Tarball write complete path including the file name.
      e.x. $:  /home/user/MyCustomTars/rootfs.tar.xz

  If files are located in a directory write the directory path
      e.x. $: /ti-sdk/targetNFS/

################################################################################

Enter path for Rootfs Partition : /home/me/tisdk/build/arago-tmp-external-arm-toolchain/deploy/images/am57xx-evm/arago-base-tisdk-image-am57xx-evm-20200411233748.rootfs.tar.xz

File exists


################################################################################

	Copying files now... will take minutes

################################################################################

Copying boot partition


Copying rootfs System partition



Syncing...

Un-mount the partitions

Remove created temp directories

Operation Finished

© 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.