Hi all, I have got the following source and installed ptx using OSELAS.BSP-Pengutronix-Mini2440-Quickstart document. OSELAS.BSP-Pengutronix-Mini2440-2012.06.0.tgz ptxdist-2012.07.0.tar.bz2 OSELAS.Toolchain-2011.11.1.tar.bz2 can you plz help with how to start with Pengutronix, i mean to create kernel and rootfs images. a step by step guide or online link wud be help full. i also http://wingston.workshopindia.com/wingz/embedded-programming-on-the-mini... but that link is not alive. so plz help me on d same. Regards, Dhruv
Pengutronix installation and setup
Something wrong with the quickstart? It describes all the steps from downloading the archives, installing required software, building the board support package (BSP) and how to deploy your Mini2440 with the result. What else do you need to know?
Once i am done withe the following with no error # mkdir ~/local # cd ~/local # tar jxvf ptxdist-2011.11.0.tar.bz2 # cd ptxdist-2011.1.0 # ./configure # make # sudo make install on passing the below command i get the following error $ ptxdist platformconfig error: 'selected_ptxconfig' file is missing try 'ptxdist select <ptxconfig>' or 'ptxdist clone <project>' to clone an existing project
You just installed PTXdist. Its a tool to be able to build all the other components to make your target work. Now you should begin with the next step: Extract the compiler toolchain archive at a different location, configure it for your target architecture and continue. To build it you need the already installed PTXdist. After you have PTXdist and the compiler toolchain in place (mostly a one-time-job), extract the Mini2440 BSP and this time use the compiler toolchain and PTXdist to build it.
Thanks for the information Juergen :) and can we modify the kernel config using PTXdist, the way be do using make menuconfig.
I was installing the pengutronix BSP according to the quickstart manual. While configuring the ptxdist with the command: $./configure I get an error as: configure:error:Please specify the location of the patch executable with the option '--with-patch' What location am I supposed to give here ?
I execute follow commands: mkdir ~/local cd ~/local tar jxvf ptxdist-2014.07.0.tar.bz2 cd ptxdist-2014.07.0 ./configure make sudo make install After this, i execute follow commands: mkdir /opt/OSELAS.Toolchain-2012.12.1 chown silart /opt/OSELAS.Toolchain-2012.12.1 chmod a+rwx /opt/OSELAS.Toolchain-2012.12.1. And: $ tar xf OSELAS.Toolchain-2012.12.1.tar.bz2 $ cd OSELAS.Toolchain-2012.12.1 $ ptxdist select ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.7.2_glibc-2.16.0_binutils-2.22_kernel-3.6 -sanitized.ptxconfig After last command i receive next error: error: 'selected_ptxconfig' file is missing try 'ptxdist select <ptxconfig>' or 'ptxdist clone <project>' to clone an existing project What is my fault?
Juergen, text from my previous post, I copy from manual. I use OSELAS.Toolchain-2013.12.2. This error occurs in ptxdist-2014.08.0 and ptxdist-2014.07.0 versions. I build ptxdist-2014.06.0 and all is ok. Command: ptxdist setup is executed successfully. When i execute this command in ptxdist-2014.08.0 or ptxdist-2014.07.0 versions, error occurred. Is it bug or feature?
juergen :: I am getting the following error .Pls give ur suggetions checking for suffix of object files... configure: error: in `/home/ism/OSELAS.Toolchain-2012.12.1/platform-arm-v4t-linux-gnueabi-gcc-4.7.2-g libc-2.16.0-binutils-2.22-kernel-3.6-sanitized/build-target/glibc-2.16.0-headers -build': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details make: *** [/home/ism/OSELAS.Toolchain-2012.12.1/platform-arm-v4t-linux-gnueabi-gcc-4.7.2-g libc-2.16.0-binutils-2.22-kernel-3.6-sanitized/state/glibc-headers.prepare] Error 1
sudhakar_G, sorry, no idea yet. Its not PTXdist which fails in your case, its the autotools based build system of the glibc. Can you have a look into the "platform-arm-v4t-linux-gnueabi-gcc-4.7.2-glibc-2.16.0-binutils-2.22-kernel -3.6-sanitized/logfile"? We (Pengutronix) have a dedicated mailing list for such questions, where you should send this logfile to. Otherwise I habe no idea how to get an idea what going wrong at your side.