So as I have been working towards dumping Windows and moving to Linux, I have some concerns with development tools and other things running in Linux.
I have a number of things that might not work in Linux. Multimeter logging, a TL866 programmer, some logic analyzers, and some instruments like a DS1054Z, DS1052E, Siglent SDG, etc...
Anybody have advice on how to make Linux work with theses kinds of things? I prefer Linux Mint as my distro.
Example - sending a SCPI command to an instrument:
$ lxi scpi --address 10.42.0.42 "*IDN?"
RIGOL TECHNOLOGIES,DS1104Z,DS1ZA171206207,00.04.03
Example - retrieve PNG screenshot:
$ rigol_1000z_screenshot 10.42.0.42 my_screen.png
Saved screenshot to my_screen.png
I didn't build up an I7 7700k box just to slow it down with virtualization. If dual booting is out of the question, how about a KVM switch? One box for Linux and the other for Windows. You can even run them both at the same time and just switch the keyboard, video and mouse.
I didn't build up an I7 7700k box just to slow it down with virtualization. If dual booting is out of the question, how about a KVM switch? One box for Linux and the other for Windows. You can even run them both at the same time and just switch the keyboard, video and mouse.The goal is ofcourse to put the stuff you use least in the VM and in my experience the hard drive is the only speed limitation so get an SSD to store the VM images on.
I didn't build up an I7 7700k box just to slow it down with virtualization. If dual booting is out of the question, how about a KVM switch?
What is everyone doing for arm? I have mplabX/pickit3 and avrdude but keep seeing threads about arm. What the fav Linux toolchain there?
For microcontroller use you can use the GCC port for ARM which is maintained by ARM: https://launchpad.net/gcc-arm-embedded (https://launchpad.net/gcc-arm-embedded)I didn't build up an I7 7700k box just to slow it down with virtualization. If dual booting is out of the question, how about a KVM switch?
Virtualization doesn't cause slowdown with Linux as a host like it does with windows as a host. If your just running one guest you won't really notice it.
What is everyone doing for arm? I have mplabX/pickit3 and avrdude but keep seeing threads about arm. What the fav Linux toolchain there?
For any ARM development (Cortex-A, Cortex-M, etc.) I always use crosstool-ng (http://crosstool-ng.github.io/ (http://crosstool-ng.github.io/)) to build a custom toolchain that I optimize for the specific chip I'm using. This way I get maximum performance and a nice gcc toolchain with gdb debugger and all the useful tools that binutils provides :-+
I have a number of things that might not work in Linux. ... DS1054Z, etc...
https://www.teuniz.net/DSRemote/ (https://www.teuniz.net/DSRemote/)
Anybody have advice on how to make Linux work with theses kinds of things? I prefer Linux Mint as my distro.
NI has or had a version of LabVIEW for GNU but it was really crippled, similar to their 64-bit version. My guess is there is little demand for it.
Anytime I have play with any of the open source code, its go out and find all the file, sub files, sub sub files. Build, build build build build. Then test test test test test. Then pick the least buggy of the various attempts. Normally asking for help in the forums is a negative result.
Does Octave now come with 64-bit indexing enabled? Last time I looked was maybe five years ago and they still were 32-bits. I think I asked in the forums and the through was there was no need to support it as you would never work with data sets that large. :-DD Fun stuff. Everyone should at least try it once.
Anytime I have play with any of the open source code, its go out and find all the file, sub files, sub sub files. Build, build build build build. Then test test test test test. Then pick the least buggy of the various attempts. Normally asking for help in the forums is a negative result.
Does Octave now come with 64-bit indexing enabled? Last time I looked was maybe five years ago and they still were 32-bits. I think I asked in the forums and the through was there was no need to support it as you would never work with data sets that large. :-DD Fun stuff. Everyone should at least try it once.
https://www.gnu.org/software/octave/doc/v4.2.0/Compiling-Octave-with-64_002dbit-Indexing.html (https://www.gnu.org/software/octave/doc/v4.2.0/Compiling-Octave-with-64_002dbit-Indexing.html)
Time to leave Windows behind mister ;)
"What do you anticipate Microsoft will do next?"
...
Microsoft will switch to Linux and keep selling their software on top of Linux. And it will cost the Windows users as much as before.
At the same time will the Linux community get face-stomped by hordes of Windows users, all trying to learn everything there is to learn about Linux and in record-breaking time.
Some long-time Linux supporters will switch to Microsoft in a heart beat like cold-hearted back-stabbers, while others die the slow death of the White Knight in the most epic drama the Linux community has ever seen, before the Linux community itself disappears and we will all have turned into "the new Windows user".
Once it's all done and over, and Microsoft has taken over Linux with its hordes of Windows users, will you either be the new slave of the Microsoft empire or you will have found refuge under a tiny bridge, just next to the one where all the FreeBSD trolls live, and where you'll then be telling tales of Linux's past.
Does Octave now come with 64-bit indexing enabled? Last time I looked was maybe five years ago and they still were 32-bits. I think I asked in the forums and the through was there was no need to support it as you would never work with data sets that large. :-DD Fun stuff. Everyone should at least try it once.
https://www.gnu.org/software/octave/doc/v4.2.0/Compiling-Octave-with-64_002dbit-Indexing.html (https://www.gnu.org/software/octave/doc/v4.2.0/Compiling-Octave-with-64_002dbit-Indexing.html)
Time to leave Windows behind mister ;)
This is exactly my point. It's been at least four years, maybe five and they still built for 32-bit. The option was there back then to build it with 64-bit indexing. Of course you then need to find and set up everything. After playing with several versions, I was able to get it working fairly decent and it actually did a decent job compared with Mathworks, considering it was free. But wow, what a time sucker. Build a version, and graphics was great but some bug. Build the next version, graphics are broke.
I ran it as a sever for over a year once without a power cycle. I thought that was pretty impressive.
One day, maybe the mainstream tools I use will run on it.
Here, most of the software testing is done in Virtualbox VMs on a Debian host.
Used VMWare in v1 days and it was good, but v2 sucked like hell so we switched to Virtualbox. Not looked at VMWare since so can't comment on recent versions, but we're happy with Virtualbox anyway. It allows you to redirect specific USB devices from host to guest. Support is USB1 only unless you install the extension pack, which is not strictly free for business use.
Honestly, there’s really no reason to dick around with WINE in my opinion.
Which of the 50 VMWare products does one choose? It isn't even close to obvious.
But getting something to work under Wine eats more time than RAM and hard drive space cost nowadays. I have tried Wine in the past but every time the first piece of software I try doesn't work.Honestly, there’s really no reason to dick around with WINE in my opinion.VM's are great, but virtualisation is a RAM and disk space eater, that is one reason why Wine is still relevant. It is also handy for software which is only used occasionally where you don't want to maintain an entire other OS just for the odd program.
But getting something to work under Wine eats more time than RAM and hard drive space cost nowadays. I have tried Wine in the past but every time the first piece of software I try doesn't work.Honestly, there’s really no reason to dick around with WINE in my opinion.VM's are great, but virtualisation is a RAM and disk space eater, that is one reason why Wine is still relevant. It is also handy for software which is only used occasionally where you don't want to maintain an entire other OS just for the odd program.
Honestly, there’s really no reason to dick around with WINE in my opinion.
VM's are great, but virtualisation is a RAM and disk space eater, that is one reason why Wine is still relevant. It is also handy for software which is only used occasionally where you don't want to maintain an entire other OS just for the odd program.
Honestly, there’s really no reason to dick around with WINE in my opinion.
VM's are great, but virtualisation is a RAM and disk space eater, that is one reason why Wine is still relevant. It is also handy for software which is only used occasionally where you don't want to maintain an entire other OS just for the odd program.
A few years ago I would have agreed with you; but now you can have 16GB of ram and 1TB of solid state storage for very little money.
I basically stopped even trying WINE awhile back because it was easier to use a VM. Keep in mind I keep the Windows 7 VM booted but paused, so it only takes a few seconds to start.
I also find a VM much handier than dual booting because of one fantastic little feature: Snapshots. Being able to take a snapshot of the entire VM (which includes memory contents if it’s running) allows you to roll back to any point instantly. It’s great for trying out new software, without botching an entire Windows install.
(I don’t know how other VM software does it, but in VMWare they essentially use “linked clones” of the virtual hard disk image to do snapshots, so you’re only saving the changed data between snapshots and not an entirely new copy of the disk image. That saves a good deal of space!)
Anyway, WINE does have its place, I’m just not a big fan. (For example, Novarm distribute their macOS version of DipTrace as a WINE bottled application, however I never quite felt it worked 100% right, despite being coded specifically with the constraints of WINE in mind. I eventually moved over to the Windows version in a VM and was much happier.)
For anything that requires a physical connections VMs can be hit and miss, the device won't always show up as an option to do pass through or sometimes it will just be flaky. My experience with that has always been mixed. I would just have a separate machine with windows for that stuff. But in general I do my best to avoid anything that may require windows. It is annoying that so many things are designed for it though instead of being open.
I’ve actually found using a VM with good USB logging capabilities can be very, very helpful when writing software for an embedded
USB stack. Also for reverse engineering protocols and hacking devices. It makes it super easy to monitor the traffic flow. [emoji4]
A VM boots in seconds (from SSD) but my Windows XP VM is always running so Windows is a mouseclick away. Schematics and PCB design work just fine in the VM as well.But getting something to work under Wine eats more time than RAM and hard drive space cost nowadays. I have tried Wine in the past but every time the first piece of software I try doesn't work.Honestly, there’s really no reason to dick around with WINE in my opinion.VM's are great, but virtualisation is a RAM and disk space eater, that is one reason why Wine is still relevant. It is also handy for software which is only used occasionally where you don't want to maintain an entire other OS just for the odd program.
It depends on the software - I posted a while back about running Sonnet Lite under Wine on my Mac and it worked fine.
I wouldn't try too hard, if it doesn't work it doesn't work and then you know a VM is the way forward. If it does work then you are up and running in less time than it takes to boot a VM :)
I’ve actually found using a VM with good USB logging capabilities can be very, very helpful when writing software for an embedded
USB stack. Also for reverse engineering protocols and hacking devices. It makes it super easy to monitor the traffic flow. [emoji4]
Better than, for example, using Wireshark?
I’ve actually found using a VM with good USB logging capabilities can be very, very helpful when writing software for an embedded
USB stack. Also for reverse engineering protocols and hacking devices. It makes it super easy to monitor the traffic flow. [emoji4]
Better than, for example, using Wireshark?
At the very least I find it’s easier to setup and much less intrusive, since you don’t need any custom drivers or low level modifications to the system (which all of the useful USB logging apps I’ve seen require).
It removes that additional abstraction layer, so I’ve found it’s less likely to interfere with what you’re trying to debug.