buildroot with the K3

[qlob]

I'm going to attempt building some programs and whatnot (like twobob has been), and it sounded like buildroot was a good place to start... Unfortunately, I have almost no experience whatsoever with compiling and the like...

Just got Buildroot to launch menuconfig, but cannot figure out what I need to choose for "Target Architecture Variant"... hmph.... Any ideas?

[knc1]

Originally Posted by qlob

I'm going to attempt building some programs and whatnot (like twobob has been), and it sounded like buildroot was a good place to start... Unfortunately, I have almost no experience whatsoever with compiling and the like...

Just got Buildroot to launch menuconfig, but cannot figure out what I need to choose for "Target Architecture Variant"... hmph.... Any ideas?

Ask twobob if he will share his BR config files.
Use those for a starting point.

There is a "set" of them, all fairly small files. Similar to the kernel's ".config" files (BR uses the same configuration system).

[qlob]

Ah wait -- never mind... found this after a bit of googling:
https://www.mobileread.com/forums/sho...d.php?t=188031

NEXT UP: Configure Buildroot: (In the make xconfig menu, you can also do gconfig or w/e)

Settings: For Kindle 3 Keyboard.
Arch: Arm (little endian)

Variant: arm1136jf_s

Target ABI: EABI

Build options, Commands, Mirrors as they are

Toolchain:

Type: External

Toolchain: Sourcery CodeBench ARM 2007.q3

Origin: Pre-installed

Path: /opt/arm-2007.q3 (or whatever)

[x] enable mmu support

[qlob]

Now I just need to find the 2007q3 toolchain... It doesn't seem to be mirrored at the KeK repo....

[knc1]

Originally Posted by qlob

Now I just need to find the 2007q3 toolchain... It doesn't seem to be mirrored at the KeK repo....

It isn't?

Go to the "appendix B" of the KeK manual - there should be a link there to the Mentor Graphics index page.

[qlob]

Originally Posted by knc1

It isn't?

Go to the "appendix B" of the KeK manual - there should be a link there to the Mentor Graphics index page.

Nope, only 2006q1 or something to that effect...

[qlob]

Don't see a link in the reference, but Im probably missing something....

EDIT: when i go to download said toolchain (from link in email), I get a "token error"

[knc1]

http://www.mentor.com/embedded-softw.../lite-edition/

In the "ARM" section, click:
Download gnu/linux ...
Register if required
Follow the download link you receive in your e-mail
Find the desired package in the list - click that link
On that release page, select the type of package (the "installer" type files can not be re-distributed, the "archive" type of files may be re-distributed).

While the file is downloading, in your downloader panel, click copy-link, find something like:
From: https://sourcery.mentor.com/public/g...ux-gnu.tar.bz2

OR:
Check the KeK resource pool for the desired archive:
[ps34532]$ ls -1 arm-2007*
arm-2007q3-51-arm-none-linux-gnueabi-i686-mingw32.tar.bz2
arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
arm-2007q3-51-arm-none-linux-gnueabi.src.tar.bz2
They are there now.

(That is the 32bit Windows binary, 32bit Linux binary, and source code bundle if the names don't mean anything to the reader.)

[knc1]

Originally Posted by qlob

Don't see a link in the reference, but Im probably missing something....

EDIT: when i go to download said toolchain (from link in email), I get a "token error"

I added them to the DIY-KeK resource pool at: http://drpbox.knetconnect.com/KeK as the file names shown above.

Under Linux:
Download file ;
sudo tar -C /opt -xf arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
export PATH=/opt/arm-2007q3/bin:$PATH
export CROSS_COMPILE="arm-none-linux-gnueabi-"
Now that instance of your terminal is ready to go for "manual makefile" use.
In Buildroot, there are fields to set the above information in.
You can also add those two export statements to your shell config file, so all shells have those settings.

[qlob]

Thanks!

[qlob]

Downloading it now, with less than 5 min to go.

EDIT: Done!

[twobob]

Hi mate.

Yeah, The completed Pass / Fail list should save you some pain.

I will probably donate my entire karma to you if you test out and fix Tiny X on the 3 first Also note that the GIT repo from BR will change over time - so perhaps take two copies (one for reference, one to update via git pull, make diffing easier later on)

I run 4 5 copies atm for similar reasons (multiple targets, copies etc)
not terrible advice.

remember to configure your device as outlined at the minimodding article and if you are going to get radical with Busybox or something ensure you go down the safe path and don't end up with a bazzilion files (I did that once) - or copies of the busybox binary over and over. check my better busybox thread for the link / alias solution if you feel the need to replace core functionality. its much safer and takes up less room.

much of the stuff in /lib (not /usr/lib) /bin and the other ROOT folders will NEVER be called as it is core the the device (and has copies on already) so figure out what you DON'T need to copy (copying takes time, transfer the FAT can be dull the 1000th time, keep it trim, don't copy redundant rubbish)

/usr is probably a really great folder to start with and go from there.

readelf -d (theApp) to check any missing bits (try just dumping it on and see what fails)
a LOT of the time, it will "just work" with the minimodding config. (and just the /usr content moved)

another trick is to prefix the stuff with /mnt/us is the makes (I now do this on the new added stuff) - but let's visit that later - when you have a file skeleton to reflect that location.

more tips:
Don't build the QT examples. (circa 2 Gb IIRC) or at least do it last. and separate out the files (usr/share/qtX/blah, I think) before passing via scp.

moving files:
WinSCP has a nice trick of unrolling all symlink on-the-fly by default when copying onto FAT via Wine. I recommend it.

finding output:
I also no longer even build an output filesystem (tarred or otherwise), I simply jump to <~/GIT/BRK3>/output/target - those are the files you want for the kindle.

splatter them (ignore everything except the /usr/* in most cases) onto FAT mirrored as-is (so often you just copy that one folder for an updated transfer of a build) and since WinScp manages all the symlink resolves... well.. cup of tea and its done

Best practices:
Originally took me maybe 20 mins of "titting about" using other methods of transfer and by-hand sym-link resolving. Honestly - the method I'm describing is MUCH quicker.
for getting "to test". (if you feel fancy later on you could rsync it or something )
It could be scripted - to 99% success - if you preferred that route.

I'm happy with cherry-picking files and fast unrolled links.

HTH.

[qlob]

Hmmmm.... That sure is quite a lot of karma.... Unfortunately, I'm completely out of my depth with buildroot...

while running make it seems i need g++ and bison... time for yum!


Thanks for the karma offer, though

[qlob]

Oh, just a question: for the prefix option in buildroot, I use arm-none-linux-gnueabi- or whatever is is, right?

[twobob]

Originally Posted by qlob

Oh, just a question: for the prefix option in buildroot, I use arm-none-linux-gnueabi- or whatever is is, right?

yep. : )

should be some screenies IIRC of those types of settings : D

possibly

EDIT: REMOVE THE SUFFIXED -
(for future readers)