Thanks Romain,
I succeeded too with Buildroot by ditching the linux-stable
4.16.18-rt12 kernel (*) for beagboard/linux 4.14.67-ti-r73 and
using Robert's am335x-boneblack-bbb-exp-c.dts.
There must be some cape driver issue to resolve in 4.16.y
Like you I think that the Beagleboard organization and its TI
sponsors would benefit having a dedicated mailing list around the
Buildroot method of embedded Linux development. TI is a Yocto
member but I prefer Buildroot simplicity. In any case, working
with BBB and friends via their own resource constrained Debian
distribution is an inconvenient method for any serious product
development...
Cheers, Enoch.
(*) Which works for me well in another BBG case.
On 09/05/2018 04:09 AM, [email protected] wrote:
Hi,
I had also some issues porting my system from Robert's
Debian image to a Buildroot config (using PRU).
I had to choose between TI or Robert's methods to add
capes, so with device tree overlays or write a single device
tree with everything hard coded.
I think it would be nice to join the effort and create a
Buildroot defconfig using Robert's patches but uBoot in order
to use the "capes manager" and using the same kernel config as
starting point.
And sorry, I have never used the LCD cape.
Sincerely,
Romain
On Saturday, August 25, 2018 at 9:59:48 PM UTC+2, Enoch wrote:
Hi,
Buildroot, to those
who are not familiar with, is a minimalist approach to
building embedded Linux.
With this approach one does software development using
desktop cross compilation tools rather than rely on Gcc
and friends running on the much slower BBB.
Modifying Linux drivers, creating one own's device tree
is easy this way.
I had good Buildroot luck with the BBB using simple
capes (for serial communication).
However, a complex cape such as the "LCD 7.0" CAP-TOUCH
BEAGLE BONE" is not an easy task "to buildroot"
for the formidable number of components (drivers,
packages, ...) that need to be correctly selected.
Has
anyone taken this BBB buildroot approach with a
similar complexity LCD cape?
Thanks,
Enoch.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in
the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/1t6VLjrzBRo/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9149a708-48a3-4bf7-bba8-0f581d4a2cd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Enoch Wexler, Embedded Systems Engineer
Voice/SMS: +1 (551) 333-9391
--
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].
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/336d17c3-18d9-163b-613d-c1ce6698af79%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
|
