# What is the correct custom\_defconfig and custom.conf for a 'custom' machine based on ccimx6ulsbc?

**URL:** <https://forums.digi.com/t/what-is-the-correct-custom-defconfig-and-custom-conf-for-a-custom-machine-based-on-ccimx6ulsbc/21062>\
**Category:** Linux\
**Tags:** linux, yocto\
**Created:** [January 23, 2020, 10:31am UTC](https://forums.digi.com/t/what-is-the-correct-custom-defconfig-and-custom-conf-for-a-custom-machine-based-on-ccimx6ulsbc/21062 "2020-01-23T10:31:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hellsmoke](https://avatars.discourse-cdn.com/v4/letter/h/919ad9/32.png) [@hellsmoke](https://forums.digi.com/u/hellsmoke)\
**Post date:** [January 23, 2020, 10:31am UTC](https://forums.digi.com/t/what-is-the-correct-custom-defconfig-and-custom-conf-for-a-custom-machine-based-on-ccimx6ulsbc/21062/1 "2020-01-23T10:31:40Z")

</div>

Hi

I included a custom machine named ‘custom’ according DIGI documentation.

I always get an error building u-boot. Some defines and structs failed during compilation.

I found out that the custom.conf and the custom\_defconfig file is the key.

I tried:

- custom\_defconfig according meta-custom layer from DIGI github =\> failed
- custom\_defconfig according ccimx6ulsbc\_defconfig from current yocto =\> failed
- using ccimx6ulsbc\_defconfig instead custom\_defconfig in custom.conf =\> compiled

How does a correct custom.conf look like?

Regards  
Michael