Hi, William - Thanks for the suggestions. I think I know Linux well enough to start learning the nuances of how its embedded features work. And, I'm already somewhat familiar with various peripheral devices. In another job, I wrote drivers/interfaces for things like I2C, SPI, UART, memory, etc. That was bare-metal programming, though, where the devices were tied to a known address and I manipulated the lines myself. I was hoping that the BBB and the book would help me learn how to do this with Linux, using the file system, but I'm starting to think this has been a waste of time and money.
I do appreciate the help you've given me, though. On Monday, February 27, 2017 at 5:20:17 PM UTC-7, William Hermans wrote: > > > > On Mon, Feb 27, 2017 at 3:13 PM, mzimmers <[email protected] <javascript:> > > wrote: > >> Hi, William - >> >> Small scale answer is that I'm trying to perform the exercises in >> Molloy's book. Large scale answer is that I'm trying to learn about >> embedded Linux, particularly as it applies to bus and peripheral interface >> programming. Just an attempt at making myself more marketable. >> > > Ok, I get it, been there myself, and to some extent I'm still there. I do > this professionally now, and like with anything. No one knows everything. > By this, I mean I'm constantly learning. > > The best advice I can offer to you, assuming you want any: Is to learn > Linux. Learn Linux well, then learn the Linux programming interface. Learn > how to work with files, as most of the devices you'll be communicating with > will be through a file like interface. Some interfaces can even be socket > like in nature. SocketCAN for example when using a CANBUS device in Linux. > At some point, you'll come to realize that all these software libraries > written by many people are all but useless. This is one of the problems I > have with the book "Exploring embedded Linux with the beaglebone black". > There is so much useless example software, that this software gets in the > way of learning how to work with the hardware, through software. So in > effect, the book in whole for me is useless, as I learn nothing from it > Granted, I know where I stand in terms of electronics engineering. e.g. I'm > about good enough to be dangerous. Luckily for me, I've a buddy who designs > hardware, and sometimes we even agree to work on a project together . . . > -- 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/ba692c84-6cde-4853-9450-2f0c24643c8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
