Modern ARM kernels will boot on many systems, BUT you have to have the right Device Tree file. So what you need to do is find the right .dbt file for that board (it is board specific not chip) and check that it is supported by the generic ARM kernel. Then it should work provided the u-boot on the device supports DT enabled kernels (otherwise you have to append the DT to the kernel).
David On Wednesday 28 October 2015 12:10:56 Jacob Juul Klejs Kolding wrote: > About a year ago this guy, http://www.hpmuseum.org/forum/thread-1789.html > > managed to compile and boot a small elf binary on the HP Prime. > > The only thing the elf does is writing pixels to the frame buffer and then > halting. > (LCD is 320x240 at 24bpp) > > The HP Prime uses a Samsung SoC ( > http://system-on-a-chip.specout.com/l/313/Samsung-S3C2416) > with with a single 400MHz ARM9 core and a LCD controller with 2D > acceleration. > > Also i read that the JTAG pins are accessible. > > Now I was thinking. > > How difficult would it be to port the the bbb kernel to this system? > > We already know that elf compiled with gcc boots on the system and we know > the address of the frame buffer. > > Only thing missing is how the keyboard interfaces, > > I have done a fair share of kernel compiles but never any actual kernel > development > > I don't know the first thing about booting/initializing a CPU/MEM/OS. > > but if someone could figure out that part I'd like to have a go at writing > a frame buffer driver for the LCD. > > What should I read up on to get a grasp on how the kernel initializes the > CPU/MEM? > > Any help would be greatly appreciated. > > Thanks! > > /Jacob -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
