DR-1000 firmware from scratch(openembedded/poky that is)

[Krambambuli]

Hello,

Since I really would like to compile the firmware for the
DR 1000S by myself using the latest poky relleases and
i havent found anything but the "outdated" binary only
iOn Environment as well as some vm images and other
"patchwork" i guess i need to start from scratch.

So i checked out the latest development poky
( git clone git://git.yoctoproject.org/poky.git )

And am starting to read up on MACHINE definitions and
how to use bitbake in generall. (poky-handbook.pdf)

Next thing for me to do would be to get the kernel configuration.
(seems that this has allready been done)

Also i do not know if all hardware is openly supported or if
there are binary only parts.

Then there is the core configuration and application selection.

finally i hope ill get.
::
better power management.

less hangs.

sd card replacement while online (on the fly bookshelf swapping)
one card with all metadata the library index one may call it
and the otheres with books and lokal bookshelf metadata.

to use the big mysterious connector with the many lines for something usefull

and last but not least. a "really" open and future update friendly
development environment for this nifty piece of tech.
::

If anyone has allready done this or has any information on this topic.
Please let me know.

Krambambuli

[Iñigo]

Hi Krambambuli,

welcome to the tiny world of IREX DR ereaders development!

your target looks very ambitious...

Originally Posted by Krambambuli

Hello,

Since I really would like to compile the firmware for the DR 1000S by myself using the latest poky relleases and i havent found anything but the "outdated" binary only iOn Environment as well as some vm images and other "patchwork" i guess i need to start from scratch.

So i checked out the latest development poky ( git clone git://git.yoctoproject.org/poky.git )

And am starting to read up on MACHINE definitions and how to use bitbake in generall. (poky-handbook.pdf)

I've tried something similar some months ago, with the hope that new cross-compilation environment could get faster binaries... I wasn't been able to build a working one. So after more investigations I continued with IREX supplied env plus a few new compilation flags.

Originally Posted by Krambambuli

Next thing for me to do would be to get the kernel configuration.
(seems that this has allready been done)

Also i do not know if all hardware is openly supported or if there are binary only parts.

Most of the firmware is open source except e-ink driver (name delta) and UDS, the official file viewer, a very important part of the device.

Originally Posted by Krambambuli

Then there is the core configuration and application selection.

finally i hope ill get.
::
better power management.

less hangs.

sd card replacement while online (on the fly bookshelf swapping)
one card with all metadata the library index one may call it
and the otheres with books and lokal bookshelf metadata.

to use the big mysterious connector with the many lines for something usefull
and last but not least. a "really" open and future update friendly
development environment for this nifty piece of tech.
::

There are much work announced in this forum.
As core components, you can look for Mackx's hack (DR1000) or DR800+, improved CTB, others.
Also I find usbnet very useful.

Originally Posted by Krambambuli

If anyone has allready done this or has any information on this topic.
Please let me know.

Krambambuli

To start, read IREX original iOn Development Document, and then build your development env (on a virtual machine or on your main linux desktop if you use one), including: cross-compiler and emulator.

There are a lot of information and code scattered in this forum. Spend some hours looking at messages title and reading some threads.

And of course, ask if have questions.

Regards,
Iñigo

[Krambambuli]

Hi Iñigo,

Sorry to here you didnt get the pojy dev environment up and running
for the Freescale MX31.

Lets see how far i get.

Regarding the iOn Deveopment environment.
I went there a few months ago, but totally dumped it and any
thoughts on fixing my dr 1000 after completing the puzzle.

Thankfully i allmost forgot about this incident

In my view this really is no descent opensource development environment.

Nothing i want to spend hours in working with for shure.

I am still reading up on the forum. Information is wide spread.
maybe i get all stuff together in a Organized way and do a
overview wiki page.

Now back to the MX31 machine definition.


Krambambuli