Dear Mike,
we port OpenADK for the TI AM33xx which runs on the phytec WEGA board
(
).
They also provide a board with the rock chip. We uses the yocto template
to get OpenADK running on it. You can have a look in the files
"target/arm/systems/phytec-wega" and "target/arm/kernel/phytec-wega"
and
see how easy the configuration is to get it basically running. Also
there is a hook in for the wega board in the installation script and you
have to adapt the target/arm/Makefile.
I relay recommend to use an embedded system instead of a full blown
ubuntu. We had very bad experience with that in the past. So my
recommendation "do not even think about ship such a system to a
customer!!!". This had cost us a lot of money and was our start with
using OpenADK.
Please have also a look on the build in update mechanism of OpenADK. We
implement it for a Kontron board and for testing on the RaspberryPI. It
makes the update secure and easy. An update is made in a passive
partition. After a reboot with the new Firmware (from the passive
partition) it gets the active partition. We build in some sanity checks
if they are passed the system will boot with the new partition.#
We also build an OpenADK for the "Deutsche Bahn" for the displays of the
rail stations. There first approach was to use an arch Linux. So they
made the same mistake we did in the past. Fortunately the did not
install the systems on the tracks yet, so we were able to install
OpenADK. Anyway the main thing is a solid updater so you can fix issues
on the customer site easily.
Best regards
Martin
we port OpenADK on an Kontron Board with EFI Bios wich was a bit pain in
the as but at the end we managed it.
Am 28.05.2018 um 09:12 schrieb Mike Thompson:
I'm very interested in determining the effort to
create a port of
OpenADK to the ASUS Tinker Board. Does anyone have experience with
OpenADK on this or other Rockchip based hardware to use as a template
to get started from?
Let me explain a little where I'm coming from with this.
Two years ago as a consultant I did a port of OpenADK to support the
Google "Project Blocks" tangible programming system for children.
See:
https://projectbloks.withgoogle.com/
The "Brain Block" in the Project Block system was powered by the
recently released Raspberry Pi Zero and I chose OpenADK was the OS.
I'm the original creator of Raspbian, but with a bit of irony, I had
to make the decision that Raspbian was not the right fit for this
project. The fact that OpenADK with stripped down kernel could boot
almost instantly and the rootfs being read-only were extremely
compelling features for an embedded Linux system that had to be VERY
robust in the hands of children. At the time I was under heavy
non-disclosure agreements with Google regarding my work with the
project so I couldn't say anything about it at the time, but I found
OpenADK to be very pleasant to work with. I don't know the current
status of things since finishing my work in 2016, but I hope that they
are continuing to use OpenADK with their research in tangible computing.
Now two years later I'm an employee at a 3D printing start-up company
where we have the need to create some robust Linux based embedded
systems for robot control using Rockchip based ARM systems -- the ASUS
Tinker Board being a fairly computationally powerful system to start
with. I could use a stripped down Ubuntu system (kids won't be
anywhere near these robots), but I think OpenADK or Yocto would be a
better embedded solution where the system just needs to work with
minimal management that a heavy Debian or Ubuntu system might entail.
If a port doesn't exist, I'm assuming I would have to get a good
understanding of the Rockchip boot process to create the first stage
and second stage bootloader (probably Uboot), a custom kernel for this
hardware, the image requirements for an SDK card and figure out how to
put it all together within OpenADK. I think I have the skills to do
this, but I'm a little weary of the time it might take to figure it
all out. Also, being a start-up, my budget is rather slim to pull in
outside help.
I wanted to get some guidance from the folks on this mailing list to
see what I might expect with regards to such a porting effort for
OpenADK. Sorry for the long email on this question.
Thanks,
Mike Thompson
_______________________________________________
dev mailing list
dev(a)openadk.org
https://mailman.openadk.org/cgi-bin/mailman/listinfo/dev