Board description

The AM3517 SOM from LogicPD contains a Texas Instruments AM3517 ARM Sitara processor and can be used with a Zoom AM3517 EVM board for prototyping purposes.


URL: https://www.logicpd.com/som/am35x-som-m2/

Test results

The Yocto Project releases in the table below have been tested by the Mender community. Please update it if you have tested this integration on other Yocto Project releases:

TODO: Update table below with Yocto Project versions tested & result. Sample data:

Yocto Project Build Runtime
pyro (2.3) :test_works: :test_works:

Build Means that the Yocto Project build using this Mender integration completes without errors and outputs images.
Runtime Means that Mender has been verified to work on the board. For U-Boot-based boards, the integration checklist has been verified.

Getting started


Configuring the build

I used the instructions at https://docs.mender.io/1.2/devices/integrating-with-u-boot and https://docs.mender.io/1.2/devices/integrating-with-u-boot/manual-u-boot-integration/providing-custom-u-boot-fw-utils to integrate with uboot. The only issues/questions I found were documented in https://groups.google.com/a/lists.mender.io/d/msg/mender/7Gv0otJS6Ng/_w-astU0AgAJ. Since this post was done before the integration checklist and I no longer have access to the platform these instructions may be out of date. Feel free to direct message me at @dwalkes with any questions.

Building the image

Build your image by running:

bitbake core-image-base

Replace core-image-base with your desired image target.

Using the build output

After a successful build, the images and build artifacts are placed in the /tmp/deploy/images directory.

The disk image (with .uefiimg suffix) is used to provision the device storage for devices without Mender running already. TI has a FLASHTOOL for this purpose, which is limited to Windows 7 32 bit or earlier and is the only way to flash the part using the ROM bootloader. A project at pyusb_pcap_replay can perform image flashing steps through Python on platforms other than Windows 7 32 bit and earlier, using a trace captured on a FLASHTOOL Windows 7 32 bit system.

On the other hand, if you already have Mender running on your device and want to deploy a rootfs update using this build, you should use the Mender Artifact files, which have .mender suffix. You can either deploy this Artifact in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client only in Standalone deployments.


See original forum post at https://groups.google.com/a/lists.mender.io/d/msg/mender/7Gv0otJS6Ng/_w-astU0AgAJ

  • The official Mender documentation explains how Mender works. This is simply a board-specific complement to the official documentation.

If this post was useful to you, please press like, or leave a thank you note to the contributor who put valuable time into this and made it available to you. It will be much appreciated!

@dwalkes Maybe if you remember can you please describe more in detail how to provision (uefiimg) to board? I think it will be helpful. Thanks.

Thanks for the suggestion Marek, I’ve updated to reference the TI FLASHTOOL.

1 Like