Jump to content
43oh

yyrkoon

Members
  • Content Count

    1,408
  • Joined

  • Last visited

  • Days Won

    34

yyrkoon last won the day on December 10 2018

yyrkoon had the most liked content!

About yyrkoon

  • Rank
    Level 4
  • Birthday 07/05/1966

Profile Information

  • Gender
    Not Telling
  • Location
    Maui

Recent Profile Visitors

4,911 profile views
  1. enl, I appreciate the sentiment. I'll tell you one thing. It's got me in the best shape I've been in years. Passed that,well it pays the bills. Not exactly the best job, but it allows me to live where I'm currently living. So not all bad. I get excited every whale season, go out with a few cameras, and come back with several awesome images of whales breaching,slapping tails, or whatever they're willing to share with us at the given time. Then, the local marine life is fairly outstanding as well. Last week, I took a road trip to the north shore( I live on the west side ) to a surf spot called
  2. Hows everyone doing ? Just curious . . . So in the last two years, I have done zero coding. The contract for the last paid programming job I had ended in December 2017. When a buddy of mine( from High school ) found out and asked me if I wanted to visit / hangout at his place for a while. Since his place was/is located on Maui . . . yeah.Enough said. So again, no coding in the last couple years. Checking the local job offers through craigslist / news paper. Not many tech jobs become available here. However with the release of the Beaglebone AI, I started to get that itch again
  3. Everything still works fine with the latest version of code::blocks, and the first version of energia on Windows 10 x64 pro. In fact, the launchpad is recognized straight out of the box, without installing drivers. That is, at least for the purpose of flashing binaries to the launchpad. IN fact I've just flashed three TSSOP-20 parts, using the launchpad using a ZIP socket adapter + 20 pin TSSOP to DIP socket adapter.
  4. As do I appreciate anyone who tries to help me too. So, when I go to try something I've never done, I usually won't ask anyone for help per se. Usually I'll look for example code, and become familiar with how, and perhaps why it works. After that, because virtually no one writes code to my own "standards", I'll write something completely from scratch, as the shortest possible example I can think of. For myself to refresh my memory later on down the road if I ever need to. Because honestly, I do not retain hardware specific information in my head. Only some semblance Of the programming lan
  5. Simple Line / mux select So, this is a variation on using GPIO, via direct memory access. The benefit to using this code, or similar. Is that there is only two syscalls for each line / mux select. Versus 12 syscalls if using the standard "Linux way" using open(), write(), read(), and close(). That's PER pin. yikes. Keep in mind, I haven't put a ton of thought into this code, so it could very well be rough around the edges, but it does work. So for our particular application. We have a Line select for AIN6 on the beaglebone. As we needed more ADC channels. Again, for our own applicati
  6. For those of you who are interested. I made it easy to find the pin info "spread sheet" info on a new git here: https://github.com/wphermans/bb-info
  7. Working with GPIO, closer to the hardware: In addition to the "traditional Linux" way of working through the file system when using hardware. One can use mmap() and /dev/mem/, when absolute performance is needed, or perhaps if one needs to minimize the load put on the processor when dealing with GPIO hardware. One does need to be aware that when doing so, all operations on the hardware used is done without the kernel knowing. This is kind of a misnomer, as Linux will "eventually" know something is happening, and adjust the sysfs entries accordingly. *Assuming*, Linux even knows such hardw
  8. Working with GPIO: So where to start. GPIO is probably one of the most easiest things to work with on a beaglebone. Once you understand a few things. First, the kernel through sysfs has no idea what pins are tied to which header pin. So one needs to find a spread sheet that will explain which header pin is attached to which GPIO pin through the sysfs file structure. The base path for the sysfs gpio path is /sys.class/gpio/. However the explanation of how all this works is fairly lengthy, and there are a lot of guides dating back to the original bealgebone(white) as to how all this works.
  9. I added a couple pictures here: https://plus.google.com/u/0/106867156582775247949 with a short explanation of each. It's much easier for me to just make post on my google+ page and then link back here. I am intentionally going slow with my project here. I want to make sure it all works out good. As it is, I will need to trim the aliminum tray part I ordered precut, to the mini ITX motherboard standard. After that, I'll also have to take measurements of the board, and mark mounting holes. Also from the mini ITX motherboard standard. EDIT: For those of you who also m
  10. How to read an ADC So this bit may seem a little odd to some. Hell I know the hardware, and wrote this really quick snippet as a demonstration, and I think it's odd. The short story here. Is that we have a pin multiplexer on AIN6, and this multiplexer selects an external channel based on a bit pattern sent to it through 3 GPIO pins. That code I won't be showing in this post. but I wanted to point out why I have an odd "mvolts" value. Which indicates maximum input voltage before the voltage limiting resistor network. e.g. the on board ADC pins can only handle 1.8v absolute maximum voltage,
  11. Read from a DS18B20 temperature sensor Again, very simple code to read from a device, and put that read information out to stdout. In this case, reading from a 1-wire DS18B20 sensor. The pin used is unimportant, so long as that pin is configurable as gpio, and is not already in use by another device. 1-wire is one of the simpler sensors to connect to a beaglebone, and can be plugged directly into one of the two headers on the beaglebone using jumper wires. You need power(3v3), ground, and a gpio pin connected. See the DS18B20 datasheet to determine which pin on the sensor is used for what
  12. So, this is partly for me, and partly for others who need a refresher, or just do not know how. But I will be making several post here over time on how to write very simply code, to do one thing, or another. These, used in conjunction with a shell script could be very useful / flexible. After several long talks with many people, including some here on these very forums. I've decided that using C, to communicate with hardware, or hardware interfaces is best as can be for many situations. However, when you need to run several tools all at once, and have output formatted in some fashion, or easil
  13. So, almost everything I need is here. There only thing I'm missing is the non conductive M3 standoff washer( dont know what else to call them ), and the actual 1/4" screws that screw into the standoffs. Just playing around today, I took the main board tray piece of aluminum I have precut, and marked out the screw holes to mount it to the case frame. How I did this was cut a piece of cardboard exactly the same size as the piece of aluminum I had cut, put it into the case, pressed down on the cardboard until I got indentations form the mounting standoffs. Then I drill out the center of these ind
  14. Yeah after watching this video on gitlab: https://www.youtube.com/watch?v=PoBaY_rqeKA I've concluded for now, it's a bit more complex than I want. Granted . . . git it's self is fairly complex too, but gitlab would be something else I had to read up on, and keep up with, when all I really want is to feel all warm and fuzzy about my data being there when I need it. I may even think about making my backup strategy even simplier than what I'm currently think it should be now. May even forgo git all together, and just use rsync in conjunction with dd or tar. For 3 layers of redundancy. But I
  15. It sounds interesting. Having a web based GUI could be useful, if that's what it is. Quite honestly though, and do keep in mind im by far not a git guru. I prefer to use tools of this nature form the command line. Honestly, I find using the tools much quicker from the command line. and this way keeps me in touch with how the tool is used. So if someday I wish to script something up, it should be trivial. Which is something else I've been doing a lot of. Which also lends a lot to readability for anyone who knows their way around a Linux system. So when working with others, like for me at work,
×
×
  • Create New...