@Russell-Pirie "...will they all fit??...." You'd need to be specific as to what they are and how they are configured in order to answer that.
I'm not sure you need to rewrite a bluetooth driver, most users would utilise "Bluez" package for bluetooth, perhaps take a look at that package and see if it meets your requirements, here's a link to the package:
I flash my devices using a bash script (well ash), it just connects to the device(s) using ipv6, uploads the firmware and then ssh's into the device and execute the firmware upgrade. You could tweak my script a bit to make it handle multiple devices at once. I did about 40 of them today using my exiting script, one by one while I was eating lunch and watching the news.
My script is here:
The other option is to boot into u-boot and flash from USB.
I'm a newer user to Arch and Linux in general. I've got a pretty robust installation running on my computer with Fluxbox, PCManFM and SLiM for the graphical side (if these matter). Everything's running pretty well at the moment except I'd like to be able to auto-mount USB storage devices. Without adding the udev rule as mentioned here (because I would like the mounting to persist through a terminal window popping open), what's the best way to have things auto-mount like they do in Ubuntu or Windows? By this I mean I would plug in a USB flash drive and it'd automatically be mounted to somewhere like /media/<device name>/ and any user (or the one running x? or something) would have permissions to view/edit/execute.
@crispyoz I hadn't considered that, but it seems that getting the display connected to the Omega LTE might be the better option, if it's possible: the Omega LTE is infinitely more compact than most LTE options I've seen and having all of the network info available to software is a huge boon. From what I can tell the Omega Dash only differs in that it has the display adapter built-in, so if I can get the display connected to the Omega LTE and use the Dash drivers or OS, the LTE should be able to drive the display.
Although I'm now tempted to grab the Dash and just plug in my display instead of the 3.2" and see if it works.
@Ioannis this thread may be of use to you:
The data sheet doesn't tell us a whole lot, have you contacted their support email address and asked them to provide further details?
I miss a step by step guide how to install the HORNET node.
I am an architect / family-father and I aim a average Joe when it comes to computer in general. But I am a big fan of the project and would like to contribute. Now I've decided to try to running a Node...
I know there is plenty of video describing the individual steps out there. But I can't understand the sequences for the various steps. Like: First you do A.... and then B..... etc ..
Can someone lead me on my way.
Thanks in advance!
@Franmcm said in Help for project:
Hi Franmcm, the omega2 + is an excellent choice for your hardware and software requirements. If you have used raspberry you will not have problems with omega2 +.
I have two external drives and I'm hoping to make finding what I have and where, by topic, much easier than "plug in and hope I'm right". Is there an easy way to do this? I'd love to scrape the file and folder list of a drive and then I suppose tag folders or subfolders by relevant subject and possibly even by importance (obviously that I'd determine) and be able to see what is where on my computer without needing to physically access a drive to be sure. I'm not sure if this is at all possible, though.
Direct Orders with Onion
We have resumed accepting orders directly from customers!
Lead time is 12 weeks and other terms will apply. See our volume ordering page for more details and to get in touch.
All Omega2 devices are now in stock at our distributors Mouser and Digikey. Check out our buy page for links for each product.
More resupply shipments will be going out in late July.
It wasn't till i consoled in on the ttyS0 pins, and monitored the boot process before figured the issue out.
The SDcard was partitioned and restored from from a backup on a Linux machine. For some reason uboot was misreading the size of SD overlay partition when booting. Wiping and reformatting the partition [with the omega2+], and rebuilding the SD /overlay partition from scratch, seems to have fixed the boot problem.
@Johann-Cunningham All the original documentation can be found here:
Since the device is quite old not many still use it so I would troubleshoot the device as I would any *nix device. If you follow the Getting Started Guide on how to connect to the console, then take a look at your network setup (ifconfig), do you have a valid IP, netmask? Can you ping your router? If yes to all of these, then can you ping 22.214.171.124, if yes then your DNS may not be configured, in which case you should check your /etc/resolv.conf for a valid DNS (nameserver) entry.