SAMA5D27 SOM1 EK Yocto Build Issues

This forum is for users of Microchip MPUs and who are interested in using Linux OS.

Moderator: nferre

kengineer
Posts: 15
Joined: Tue Oct 31, 2017 3:08 pm

SAMA5D27 SOM1 EK Yocto Build Issues

Tue Oct 31, 2017 3:38 pm

I am trying to build Yocto for the SAMA5D27 SOM1 EK board following this procedure and am running into some issues partway through the build:

linux4sam/bin/view/Linux4SAM/PokyBuild# ... y_for_AT91

When running "bitbake core-image-minimal" I get the following output:

Code: Select all

bitbake core-image-minimal
Loading cache: 100% |###############################################################| Time: 0:00:02
Loaded 2683 entries from dependency cache.
Parsing recipes: 100% |#############################################################| Time: 0:00:01
Parsing of 1977 .bb files complete (1976 cached, 1 parsed). 2684 targets, 340 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task censored dependencies

Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "sama5d27-som1-ek-sd"
DISTRO            = "poky-atmel"
DISTRO_VERSION    = "2.2.2"
TUNE_FEATURES     = "arm armv7a vfp thumb neon       callconvention-hard       cortexa5"
TARGET_FPU        = "hard"
meta              
meta-poky         
meta-yocto-bsp    = "morty:1d92cb1a20135cfffff9f94a6633ec0840518738"
meta-atmel        = "morty:ed14b726cfd0d84a1f1326f246db84eecd930788"
meta-oe           
meta-networking   
meta-python       
meta-ruby         
meta-multimedia   = "morty:b40116cf457b88a2db14b86fda9627fb34d56ae6"
meta-qt5          = "HEAD:5df9d273194e89498ea7fa93ac4ec987007253d2"

Initialising tasks: 100% |##########################################################| Time: 0:00:12
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-minimal-1.0-r0 do_image_wic: Function failed: do_image_wic (log file is located at /media/user/8dd48c66-bace-4b39-88c4-9d6842b15bbf/yocto/poky/build-atmel/tmp/work/sama5d27_som1_ek_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.10619)
ERROR: Logfile of failure stored in: /media/user/8dd48c66-bace-4b39-88c4-9d6842b15bbf/yocto/poky/build-atmel/tmp/work/sama5d27_som1_ek_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.10619
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_wic
| Warning: bootloader config not specified, using defaults
| Error: exec_cmd: install -m 0644 -D /media/user/8dd48c66-bace-4b39-88c4-9d6842b15bbf/yocto/poky/build-atmel/tmp/deploy/images/sama5d27-som1-ek-sd/BOOT.BIN /media/user/8dd48c66-bace-4b39-88c4-9d6842b15bbf/yocto/poky/build-atmel/tmp/work/sama5d27_som1_ek_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-sama5d27-som1-ek-sd-20171031130633/build/boot/BOOT.BIN returned '1' instead of 0
| Checking basic build environment...
| Done.
| 
| Creating image(s)...
| 
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_wic (log file is located at /media/user/8dd48c66-bace-4b39-88c4-9d6842b15bbf/yocto/poky/build-atmel/tmp/work/sama5d27_som1_ek_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.10619)
ERROR: Task (/media/user/8dd48c66-bace-4b39-88c4-9d6842b15bbf/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_wic) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1758 tasks of which 1757 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /media/user/8dd48c66-bace-4b39-88c4-9d6842b15bbf/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_wic
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

According to the log, the initial failure happens when calling " install -m 0644 -D" on "..../core-image-minimal-sama5d27-som1-ek-sd-20171031130633/build/boot/BOOT.BIN"


When I check this directory, the "BOOT.BIN" file does not exist. The directory does contain other files however:

Code: Select all

modules--4.9+git0+973820d8c6-r0-sama5d27-som1-ek-sd-20171030193030.tgz
modules-sama5d27-som1-ek-sd.tgz
u-boot.bin
u-boot-sama5d27-som1-ek-sd.bin
u-boot-sama5d27-som1-ek-sd-v2017.03-at91+gitAUTOINC+5642d172b9-r0.bin
zImage
zImage--4.9+git0+973820d8c6-r0-at91-sama5d27_som1_ek-20171030193030.dtb
zImage--4.9+git0+973820d8c6-r0-at91-sama5d27_som1_ek_pda4-20171030193030.dtb
zImage--4.9+git0+973820d8c6-r0-at91-sama5d27_som1_ek_pda7-20171030193030.dtb
zImage--4.9+git0+973820d8c6-r0-at91-sama5d27_som1_ek_pda7b-20171030193030.dtb
zImage--4.9+git0+973820d8c6-r0-sama5d27-som1-ek-sd-20171030193030.bin
zImage-at91-sama5d27_som1_ek.dtb
zImage-at91-sama5d27_som1_ek_pda4.dtb
zImage-at91-sama5d27_som1_ek_pda7b.dtb
zImage-at91-sama5d27_som1_ek_pda7.dtb
zImage-sama5d27-som1-ek-sd.bin

Not sure why this is happening as I am new to using Yocto and the SAMA environment. I will note that when I first tried building, I had mistakingly setup the configuration for "MACHINE ??= "sama5d3-xplained"" This build was successful, but upon realizing I had put the incorrect target, I deleted the build directory and started from scratch.
kengineer
Posts: 15
Joined: Tue Oct 31, 2017 3:08 pm

Re: SAMA5D27 SOM1 EK Yocto Build Issues

Thu Nov 02, 2017 3:18 pm

My initial build was on an Ubuntu machine so just to confirm this wasn't something with my setup, I repeated the build steps on a Fedora machine with the exact same results.

Just ordered a dev board but am kind of dead in the water here right now so any help would be greatly appreciated.
blue_z
Location: USA
Posts: 1785
Joined: Thu Apr 19, 2007 10:15 pm

Re: SAMA5D27 SOM1 EK Yocto Build Issues

Fri Nov 03, 2017 2:00 am

Try a build for "sama5d27-som1-ek" instead.

Regards
kengineer
Posts: 15
Joined: Tue Oct 31, 2017 3:08 pm

Re: SAMA5D27 SOM1 EK Yocto Build Issues

Fri Nov 03, 2017 2:08 pm

It does not work as that is not on the list of valid machines:

Supported SoCs / MACHINE names
==============================
- SAMA5D2 product family / sama5d2-xplained, sama5d27-som1-ek-sd
- SAMA5D4 product family / sama5d4ek, sama5d4-xplained
- SAMA5D3 product family / sama5d3xek, sama5d3-xplained
- AT91SAM9x5 product family (AT91SAM9G15, AT91SAM9G25, AT91SAM9X25, AT91SAM9G35 and AT91SAM9X35) / at91sam9x5ek
- AT91SAM9RL / at91sam9rlek
- AT91SAM9G45 / at91sam9m10g45ek

Code: Select all

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Please set a valid MACHINE in your local.conf or environment

One thing that did allow the build to finish is copying the uboot image to the file that it is looking for "BOOT.BIN." However I'm not sure if this is correct. It appears that it is picking "BOOT.BIN" because as the warning says before the failure:

Warning: bootloader config not specified, using defaults
Not sure how to set this up correctly.
blue_z
Location: USA
Posts: 1785
Joined: Thu Apr 19, 2007 10:15 pm

Re: SAMA5D27 SOM1 EK Yocto Build Issues

Fri Nov 03, 2017 9:24 pm

kengineer wrote:It does not work as that is not on the list of valid machines:
Sorry for the misdirection. That board name is in four recipes, so I thought it might be worth a try.

kengineer wrote:One thing that did allow the build to finish is copying the uboot image to the file that it is looking for "BOOT.BIN."
BOOT.BIN is a renamed (or a link to an) AT91Bootstrap binary, not a U-Boot binary. Note that a AT91Bootstrap binary may have "uboot" in its filename because that is the object it will load.

Regards

Return to “LINUX”

Who is online

Users browsing this forum: No registered users and 3 guests