Embedded Intel® Core™ Processors
Communicate Intel® Core™ Hardware, Software, Firmware, Graphics Concerns
1194 Discussions

Intel BLDK Build Environment Setup

HS1
Novice
3,298 Views

Hi,

I am trying to setup BLDK build environment in Fedora 14.

Following is the details from Readme:

- Fedora 14 was used for all development and testing.

- This is the only supported OS available for building.

- The following tools come standard with Fedora 14 x86_64 and are the only tools

that have been validated and used by our internal development team. This is

the only build environment that will be supported.

- gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC)

- GNU ld version 2.20.51.0.7-8.fc14 20100318

- GNU Make 3.82

- GNU assembler version 2.20.51.0.7 (i686-redhat-linux) using BFD version version

2.20.51.0.7-8.fc14 20100318

- Intel ACPI Component Architecture

ASL Optimizing Compiler version 20120913-32 [Oct 11 2012]

Copyright (c) 2000 - 2012 Intel Corporation

Supports ACPI Specification Revision 5.0

This suggests installing Fedora 14. But the IASL version mentioned is of fc19.rpm and I am unable to install it successfully.

Has anybody already setup Linux BLDK Build environment? Can you please guide me

0 Kudos
1 Solution
Adolfo_S_Intel
Moderator
1,831 Views

Hello hazzel

Could you pleas try using a fresh Fedora 14 installation and using the default versions that come from the Fedora 14 repositories, by executing the following commands:

yum install iasl libuuid-devel

yum groupinstall development-tools

Please try it and let me know the results.

Best Regards,

Adolfo

View solution in original post

0 Kudos
21 Replies
Josue_C_Intel
Employee
1,731 Views

Hello Hazzel S.

Welcome to Intel® Embedded Community.

We are checking your thread and will post an update as soon as possible.

Regards.

Josue.

Josue_C_Intel
Employee
1,731 Views
HS1
Novice
1,731 Views

Hi Josue,

The Intel BLDK is got from http://businessportal.intel.com/ businessportal.intel.com

Additional Info

I tried to build BLDK under Intel for Atom Processor (Baytrail) using Ubuntu 12.04 build environment

I modified the build.sh to use /bin/bash

And then it throw few errors - Invalid stage1.ld and stage2.ld files. When I checked those files manually, I can see "-e" is appended before "Memory". After manually removing "-e" from the .ld files, I am able to generate rom.bin successfully

My problem is that when I try to flash the rom.bin, it does not starts. When I compared the rom.bin generated with the BLDK and the one provided in the package, the difference in the new image is that 0xFF are placed in first 0x20 places, and then the actual image binary starts.

Following is my questions:

1) Is changing the shell to /bin/bash is correct way?

Since this was not successful, I am trying to setup Fedora build environment as suggested

0 Kudos
HS1
Novice
1,731 Views

Hi @jc

I will get the required information and get back by Monday

0 Kudos
Adolfo_S_Intel
Moderator
1,731 Views

Hello hazzel

Could you please tell me what message error are you getting when you try to install the IASL compiler on Fedora 14?

Best Regards,

Adolfo.

0 Kudos
HS1
Novice
1,731 Views

Hi @AdolfoS

While trying to install iasl 20120913-32 [Oct 11 2012] , I got errors like "libc.so.6" not found.

I upgraded to Fedora 15 and I am able to successfully install it and also successfully generate rom.bin

But it seems to be an invalid image. Please check the attached image. Right side shows a valid image and the left one is the image generated after building with BLDK. The first 0x20 places are filled with 0xFF and flashing this rom.bin, the system does not recognize a valid image and Post code stays at 0x00.

Please help me in moving forward.

0 Kudos
Adolfo_S_Intel
Moderator
1,731 Views

Hello hazzel

Could you please indicate what is the document number of the BLDK version that you downloaded from the Business Portal? Also what is the complete name of the code base that you are using.

It would be best to try to install the BLDK on Fedora 14. The command rpm -R should list all the dependencies that the iasl package requires.

Best Regards,

Adolfo

HS1
Novice
1,731 Views

The DocID is 520786

The code base - BAYTRAIL_OTM

0 Kudos
Adolfo_S_Intel
Moderator
1,731 Views

Hello hazzel

Could you please provide the list of dependencies that you get when you try to install the iasl package?

Also what version of the BLDK tools are you using? If you download the BLDK tools from the business portal please provide the CDI number.

Thanks.

0 Kudos
HS1
Novice
1,731 Views

AdolfoS

Regarding Dependencies,

rpm -pqR /media/UUI/iasl-20120913-6.fc19.x86_64.rpm

libc.so.6()(64bit)

libc.so.6(GLIBC_2.14)(64bit)

libc.so.6(GLIBC_2.2.5)(64bit)

libc.so.6(GLIBC_2.3)(64bit)

rpmlib(CompressedFileNames) <= 3.0.4-1

rpmlib(FileDigests) <= 4.6.0-1

rpmlib(PayloadFilesHavePrefix) <= 4.0-1

rtld(GNU_HASH)

rpmlib(PayloadIsXz) <= 5.2-

The version of BLDK is OTMGOLD003

0 Kudos
Adolfo_S_Intel
Moderator
1,731 Views

Hello hazzel

Sorry for the delay in the reply.

Have you tried adding the fedora 19 repository to your distribution?

Here are the instructions to add a new repositories to Fedora: https://docs.fedoraproject.org/en-US/Fedora/18/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.html 5.3.5. Adding, Enabling, and Disabling a Yum Repository

The Fedora 19 urls should be on the files contained in /etc/yum.repos.d/

Or you might consider downloading the packages directly from a Fedora 19 distro and then copy and install them on your system, this might be useful if you want to test this option: https://access.redhat.com/solutions/10154 https://access.redhat.com/solutions/10154

I hope this information is useful to you.

Best Regards,

Adolfo Sanchez

0 Kudos
HS1
Novice
1,731 Views

Hi AdolfoS

I am able to setup the build environment and after the build is complete, the generated rom.bin image looks the same way I have already mentioned in previous posts. (The first 0x20 places are filled with 0xFF and flashing this rom.bin, the system does not recognize a valid image and Post code stays at 0x00.)

I followed the following build procedure:

1) Change to the BLDK directory

2) ./build/build_bayley_bay.sh

Flashed as below:

1) Took the rom.bin from brd_bayleybay/elf/rom.bin

2) Copied it to top 1 MB region using dediprog batch operation

Region 1 from 700000 to 7fffff

Please suggest how to move forward

0 Kudos
Adolfo_S_Intel
Moderator
1,731 Views

Hello hazzel

We are still working on this issue, and we hope to contact you with more information as soon as possible

0 Kudos
Adolfo_S_Intel
Moderator
1,731 Views

Hello @hazzel

Could you please provide more information about the commands and steps that you are following to build the image?

Best Regards,

Adolfo

0 Kudos
HS1
Novice
1,731 Views

Hi AdolfoS

Please find the attachment for the steps executed

0 Kudos
Adolfo_S_Intel
Moderator
1,731 Views

Hello hazzel

I got feedback from the engineering team, they report seeing the same issue that you are experiencing, when they use Fedora 19, but they don't observe any issue on Fedora 14.

Could you please clarify what O.S. are you using to build the image?

Best Regards,

Adolfo.

HS1
Novice
1,731 Views

Hi AdolfoS

I installed FC 14 and I am unable to install iasl-20120913-6.fc19.x86_64.rpm in FC14.

As per your suggestion I added FC19 repos to the distribution and then on installing iasl, it got upgraded to FC19.

Can you/your engineering team suggest how to setup an FC14 Build environment?

Thanks,

Manimehalai S

0 Kudos
Adolfo_S_Intel
Moderator
1,832 Views

Hello hazzel

Could you pleas try using a fresh Fedora 14 installation and using the default versions that come from the Fedora 14 repositories, by executing the following commands:

yum install iasl libuuid-devel

yum groupinstall development-tools

Please try it and let me know the results.

Best Regards,

Adolfo

0 Kudos
HS1
Novice
1,547 Views

Hi AdolfoS,

Finally figured out the problem. Additionally I had to use the below commands(especially i686 related stuffs) to do the setup:

yum install gcc-c++ libcap-devel libcurl-devel libIDL-devel libstdc++-static \

libxslt-devel libXmu-devel openssl-devel pam-devel pulseaudio-libs-devel \

python-devel qt-devel SDL_ttf-devel SDL-static texlive-latex wine-core \

device-mapper-devel wget subversion subversion-gnome kernel-devel \

glibc-static zlib-static glibc-devel.i686 libstdc++.i686 libpng-devel

 

Thanks for helping.

Reply