SamyGO

Posted: **Sun Aug 18, 2013 9:10 pm**

/opt/arm_v7_vfp_le/bin/arm_v7_vfp_le-gcc -v
no such files or directory
but the binary is present
i tried the toolchain from samygo svn t-valdeuc and the toolchain from sources ue32c6500 and ue40c8000 always i get the same error.
but in the how to build the instructions are different from these that i've found here in how to build from sams says
* Building kernel:
* Unpack the kernel tarball and cd into it.
* Run "make Image".
Maybe i've to try with VDLinux-armv7a8-toolchain-lite_20100630? but this is for d series am i right?
what is the "VDLinux toolchain for c series"?

Posted: **Sun Aug 18, 2013 9:41 pm**

are you working as root user?

Posted: **Sun Aug 18, 2013 9:42 pm**

Mk? wrote: no the uboot sources that i've are 4.295.723 and not 4 259 723.

Oops - sorry, a typo. The file I have is 4 295 723 too (MD5: 50299c641170e8844464579d338b38cf). I think we both have the same sources. And they still don't look all that promising

. Apparently it's more or less random (?), rather ancient, Samsung-modified uboot variant. I don't see any config/code/definitions for Valencia/Aquila platform in there. Even the code & config for older Chelsea/Leonid (B-series) is missing.

Honestly, I have no idea why were such old uboot sources included in the C630 open source package (and whoever prepared that package for Samsung OSRC apparently did not have any idea either).

Posted: **Sun Aug 18, 2013 10:05 pm**

sbav1 wrote:
Mk? wrote: no the uboot sources that i've are 4.295.723 and not 4 259 723.
Oops - sorry, a typo. The file I have is 4 295 723 too (MD5: 50299c641170e8844464579d338b38cf). I think we both have the same sources. And they still don't look all that promising . Apparently it's more or less random (?), rather ancient, Samsung-modified uboot variant. I don't see any config/code/definitions for Valencia/Aquila platform in there. Even the code & config for older Chelsea/Leonid (B-series) is missing.

Honestly, I have no idea why were such old uboot sources included in the C630 open source package (and whoever prepared that package for Samsung OSRC apparently did not have any idea either).

have you find the dtv_bml_aquila? have you look at it? maybe you understand more than me...
if they don't release the sources for c series that are some reason...
now if you look at oss site every c series sources was deleted...

the otp lock in sm do nothing i try my tv reboot and that's it nothing new...now i've to understand and research about boot param..."aging" in top debug menu there are 3 options boot param aging, factory reset, and another that i don't remember and i found too the option get/set secure boot authentication but i don't find info about it.
i think that only some config files are missing the set of file maybe are the same.

Posted: **Sun Aug 18, 2013 10:06 pm**

juuso wrote:are you working as root user?

yes
sudo su
and then command to avoid permissin problems

Posted: **Mon Aug 19, 2013 2:09 pm**

@ juuso
today i donwload from svn the toolchain copy it to opt/
rename the folder to arm_v7_vfp_le
then i make one folder in opt and call it src
in it i extracted the file linux.tgz form UE40C8000.zip
then i copy from /opt/src/linux/arch/arm/configs/SELP.4.3.x.valencia.def.config file
one to /opt/arm_v7_vfp_le/ and one to /opt/src/linux/
I export the path

Code: Select all

export PATH=$PATH:/opt/arm_v7_vfp_le/bin

i verify that the path is export

Code: Select all

root@sam-virtual-machine:/opt/src/linux# echo $PATH
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/arm_v7_vfp_le/bin:/opt/arm_v7_vfp_le/bin

and it seems to see right
then i cd to opt/src/linux/
and do

Code: Select all

make ARCH=arm CROSS_COMPILE=arm_v7_vfp_le- oldconfig

everything seems be ok
then

Code: Select all

make ARCH=arm CROSS_COMPILE=arm_v7_vfp_le- prepare scripts

and i get

Code: Select all

root@sam-virtual-machine:/opt/src/linux# make ARCH=arm CROSS_COMPILE=arm_v7_vfp_le- prepare scripts
make: arm_v7_vfp_le-gcc: command not found
scripts/kconfig/conf -s arch/arm/Kconfig
kernel/power/Kconfig:375:warning: choice values currently only support a single prompt
kernel/power/Kconfig:381:warning: choice values currently only support a single prompt
kernel/power/Kconfig:363:warning: choice values currently only support a single prompt
kernel/power/Kconfig:369:warning: choice values currently only support a single prompt
make: arm_v7_vfp_le-gcc: command not found
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  SYMLINK include/asm-arm/arch -> include/asm-arm/arch-sdp
  Generating include/asm-arm/mach-types.h
  CHK     include/linux/utsrelease.h
  UPD     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-arm
  CC      arch/arm/kernel/asm-offsets.s
/bin/sh: 1: arm_v7_vfp_le-gcc: not found
make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 127
make: *** [prepare0] Error 2

I'm on ubuntu 13 root user, i activate the root user and login as root to avoid permissions problems,
the path is exported to bash.rc
As you can see the gcc binary is present in bin directory

Code: Select all

root@sam-virtual-machine:/opt/arm_v7_vfp_le# ls -la
drwxrwxr-x 12 root root  4096 ago 19 10:29 .
drwxr-xr-x  4 root root  4096 ago 19 14:30 ..
drwxrwxr-x  4 root root  4096 ago 19 10:19 armv7fl-montavista-linux-gnueabi
drwxrwxr-x  2 root root  4096 ago 19 10:27 bin
drwxrwxr-x  6 root root  4096 ago 19 10:19 doc
drwxrwxr-x  2 root root  4096 ago 19 10:19 include
drwxrwxr-x  2 root root  4096 ago 19 10:29 info
drwxrwxr-x  3 root root  4096 ago 19 10:19 lib
drwxrwxr-x  4 root root  4096 ago 19 10:29 man
-rw-r--r--  1 root root 25858 ago 31  2009 SELP.4.3.x.valencia.def.config
drwxrwxr-x  3 root root  4096 ago 19 10:19 share
drwxrwxr-x  7 root root  4096 ago 19 10:26 target
drwxrwxr-x  5 root root  4096 ago 19 10:29 testsuite
root@sam-virtual-machine:/opt/arm_v7_vfp_le# cd bin
root@sam-virtual-machine:/opt/arm_v7_vfp_le/bin# ls -la
drwxrwxr-x  2 root root    4096 ago 19 10:27 .
drwxrwxr-x 12 root root    4096 ago 19 10:29 ..
-rwxrwxr-x  1 root root 2157815 ago 19 10:27 arm_v7_vfp_le-addr2line
-rwxrwxr-x  1 root root 2274246 ago 19 10:27 arm_v7_vfp_le-ar
-rwxrwxr-x  1 root root 3396269 ago 19 10:27 arm_v7_vfp_le-as
-rwxrwxr-x  1 root root  416805 ago 19 10:27 arm_v7_vfp_le-c++
-rwxrwxr-x  1 root root 2128332 ago 19 10:27 arm_v7_vfp_le-c++filt
-rwxrwxr-x  1 root root  415740 ago 19 10:27 arm_v7_vfp_le-cpp
-rwxrwxr-x  1 root root  416805 ago 19 10:27 arm_v7_vfp_le-g++

-rwxrwxr-x  1 root root  414037 ago 19 10:27 arm_v7_vfp_le-gcc

-rwxrwxr-x  1 root root   83307 ago 19 10:27 arm_v7_vfp_le-gcov
-rwxrwxr-x  1 root root 2696894 ago 19 10:27 arm_v7_vfp_le-gdb
-rwxrwxr-x  1 root root 2518358 ago 19 10:27 arm_v7_vfp_le-gprof
-rwxrwxr-x  1 root root 3146810 ago 19 10:27 arm_v7_vfp_le-ld
lrwxrwxrwx  1 root root      26 ago 19 14:24 arm_v7_vfp_le-ldd -> arm_v7_vfp_le-prelink-rtld
-rwxrwxr-x  1 root root 2192453 ago 19 10:27 arm_v7_vfp_le-nm
-rwxrwxr-x  1 root root 2708473 ago 19 10:27 arm_v7_vfp_le-objcopy
-rwxrwxr-x  1 root root 2979587 ago 19 10:27 arm_v7_vfp_le-objdump
-rwxrwxr-x  1 root root 1841027 ago 19 10:27 arm_v7_vfp_le-prelink
-rwxrwxr-x  1 root root  787329 ago 19 10:27 arm_v7_vfp_le-prelink-rtld
-rwxrwxr-x  1 root root 2274245 ago 19 10:27 arm_v7_vfp_le-ranlib
-rwxrwxr-x  1 root root  508422 ago 19 10:27 arm_v7_vfp_le-readelf
-rwxrwxr-x  1 root root 2181763 ago 19 10:27 arm_v7_vfp_le-size
-rwxrwxr-x  1 root root 2161533 ago 19 10:27 arm_v7_vfp_le-strings
-rwxrwxr-x  1 root root 2708472 ago 19 10:27 arm_v7_vfp_le-strip
lrwxrwxrwx  1 root root      47 ago 19 14:24 arm_v7_vfp_le-testbinutils -> ../testsuite/binutils/mv-test-cross-binutils.sh
lrwxrwxrwx  1 root root      37 ago 19 14:24 arm_v7_vfp_le-testgcc -> ../testsuite/gcc/mv-test-cross-gcc.sh
lrwxrwxrwx  1 root root      37 ago 19 14:24 arm_v7_vfp_le-testgdb -> ../testsuite/gdb/mv-test-cross-gdb.sh
root@sam-virtual-machine:/opt/arm_v7_vfp_le/bin#

so what i'm doing wrong? maybe the config files is wrong?
have you test the toolchain on svn?
how to fix this?
Maybe there are missing dependencies?
is there someone that has recompile the valencia kernel with success?
another questions i read that for uboot is not needed to recompile the kernel is such as a standalone program is this true?

Posted: **Tue Aug 27, 2013 6:05 am**

no idea what's wrong. later I try all by self. Yes for uboot you don't need to compile kernel, but you need it to be sure you have fully working toolchain.

Posted: **Wed Aug 28, 2013 7:47 am**

I compiled kernel with toolchain from svn and sources from c650 (sorry, dont have ones from c8000). Config i used is:

config_valdeuc.zip

You dont need kernel for u-boot, but you need working toolchain against your kernel sources (or maybe not - but anyway - it is better to have checked toolchain...)
If you fail, then i think it is your problem with environment/permissions and so on...

Posted: **Wed Aug 28, 2013 11:56 am**

juuso wrote:I compiled kernel with toolchain from svn and sources from c650 (sorry, dont have ones from c8000). Config i used is:
config_valdeuc.zip
You dont need kernel for u-boot, but you need working toolchain against your kernel sources (or maybe not - but anyway - it is better to have checked toolchain...)
If you fail, then i think it is your problem with environment/permissions and so on...

ok i set up a centos vmvare image to try again
where i have to put this config files?
is good for uc8000 sources too? could you explain where to find this?
is which dir?
tried again but i have the same error...
I think i need gcc is this the problem but on in c8000 source the gcc files are missing and in samsung opensource site too so i don't know what to do.

Posted: **Wed Aug 28, 2013 8:55 pm**

rename this config to .config and copy it to .config.old on root of your sources. I think it is good for all valencia devices.

try ubuntu vmware image.

SamyGO

U-boot sources from c series find how to cross-compile it?

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i

Re: U-boot sources from c series find how to cross-compile i