I've got a programming device called USB AVR JTAG-ISP v. 1.2.
Where can I find drivers and a good IDE for it?
For Windows, AVR Studio 4 as per the other answer.
For Linux, you want the avr-gcc and AVRDUDE packages from your OS distribution, plus your choice of C IDEs for Linux.
For OS X, you want Crosspack and Xcode.
On Linux or OS X, depending on which device you are programming, you may need to download the source for AVRDUDE and rebuild it, which will require that you also get libusb 0.1.12 (not libusb 1.x).
Try the "AVR Studio 4" on Atmel's website.
I find AVR studio to be infuriating, buggy and generally terrible.
Eclipse (available on all platforms) has wonderful end-to-end AVR integration available if you install the avr plugin, avr-gcc and avrdude.
If you're running on Ubuntu beware that it doesn't always identify the ISP right off the bat
Related
If Mbed OS is open source then why do you have to use a cloud compiler to compile the software? Is the source code for Mbed OS open but the the cloud compiler is closed source?
Just looking for clarification amongst marketing jargon.
SW
There seems to be some confusion here between Mbed OS which is a open source project and the Mbed Compiler Service, which is a tool that makes getting started with Mbed OS super easy.
Mbed OS is open source, you can find it here : http://github.com/armmbed/mbed-os, i encourage you to contribute by submitting a Pull Request.
The online compiler service is run by the Arm Mbed team to provide an easy way to get started with compiling your programs (there are some assumptions and sensible defaults in place so everything 'just works'). You can export your programs to a 3rd party compiler like Keil, IAR, or GCC / Eclipse for debugging if you need it. You can also use Mbed CLI offline to compile your code using GCC. (Fun fact, Mbed CLI is the same set of command line tools the online compiler uses).
Additional fun fact, the online compiler is using armcc (the same one that comes with Keil) where as GCC is the default for Mbed CLI (though if you have a liscense for armcc or iarcc you can use those with Mbed CLI as well.
Mbed OS is completely open source. There are various options to compile. So far, there are 3 toolchains that are supported by ARM mbed:
GCC ARM
ARMCC
IAR
Out of these 3, only GCC ARM is free while others have free evaluation versions with limited features unless you buy them.
In short, you can download mbed OS and then compile it for a target using any of the toolchains which may or may not be open source.
I heard that it has been ported to multiple virtualization platforms and switching chipsets? what does the virtualization platforms and switching chipsets mean here? what is the difference between them?
another question is :can we install the openvswitch on the bare metal switch or router?I mean can we install it on just hardware without any operating system?
From OVS FAQ, which is readily available with a Google search:
Q: What virtualization platforms can use Open vSwitch?
A: Open vSwitch can currently run on any Linux-based virtualization
platform (kernel 2.6.32 and newer), including: KVM, VirtualBox, Xen,
Xen Cloud Platform, XenServer. As of Linux 3.3 it is part of the
mainline kernel. The bulk of the code is written in platform-
independent C and is easily ported to other environments. We welcome
inquires about integrating Open vSwitch with other virtualization
platforms.
Q: How can I try Open vSwitch?
A: The Open vSwitch source code can be built on a Linux system. You can
build and experiment with Open vSwitch on any Linux machine.
Packages for various Linux distributions are available on many
platforms, including: Debian, Ubuntu, Fedora.
You may also download and run a virtualization platform that already
has Open vSwitch integrated. For example, download a recent ISO for
XenServer or Xen Cloud Platform. Be aware that the version
integrated with a particular platform may not be the most recent Open
vSwitch release.
Q: Does Open vSwitch only work on Linux?
A: No, Open vSwitch has been ported to a number of different operating
systems and hardware platforms. Most of the development work occurs
on Linux, but the code should be portable to any POSIX system. We've
seen Open vSwitch ported to a number of different platforms,
including FreeBSD, Windows, and even non-POSIX embedded systems.
By definition, the Open vSwitch Linux kernel module only works on
Linux and will provide the highest performance. However, a userspace
datapath is available that should be very portable.
Q: What's involved with porting Open vSwitch to a new platform or switching ASIC?
A: The PORTING document describes how one would go about
porting Open vSwitch to a new operating system or hardware platform.
Comparison of virtualzation platforms: https://en.wikipedia.org/wiki/Comparison_of_platform_virtualization_software
Regarding your last question: You need an underlying OS (e.g. Linux)
Another easy way to experiment with sdn , openvswitch and open flow is mininet.
They have a vm you can download and use with virtualbox, vmware etc
http://mininet.org/
http://mininet.org/download
Is installing MONO on an IBM RISC running AIX possible and or practical?
And if so where do I start?
AIX is not one of Mono's supported platforms.
From the FAQ:
Mono currently runs on Linux, Windows, Solaris, FreeBSD and MacOS X. The Just-In-Time engine (JIT) is available on x86 and PowerPC, Sparc and S390 processors and can generate code and optimizations tailored for a particular CPU. Interpreters exist for the Itanium, HP-PA, StrongARM CPUs.
You could always download the source, and compile it yourself, after working out the platform specifics. Namely, the JITter would need to be ported to handle the processor.
Since Mac virtualization is technically illegal on anything but a Mac computer, is it possible to use one of the Darwin distros as a platform to test applications meant for Mac OSX?
From the little I've read, it seems *Darwin and MacOSX have a very tight relationship, but I haven't really found any information on the internet about using Darwin for MacOSX development -- So I'm a little skeptical if it is even possible.
Has anyone tried it?
Darwin does not have Aqua or any of the Core technologies, so only pure POSIX apps can be tested.
I'm doing a little app that I want to distribute in different platforms, at least the 3 major ones.
Is it possible to use only Windows has the host OS to compile the binaries for Linux, Mac OS X and other supported platforms without resorting to virtual machines?
Or should I ask around in some community to help me compile on, well OS X, actually, since I can virtualize a Linux machine quite easy?
It is possible to compile from one plateform to another, it is called cross-compilation. You will find extensive informations at http://www.stack.nl/~marcov/buildfaq.pdf
The buildfaq above contains sample cross-compilation :
from Windows to Linux,
from FreeBSD to AMD64 Linux
The FPC download page contains :
the i386-win32 to x86_64-win64 cross-compiler
the i386-win32 to arm-wince cross-compiler
The FPC mailing lists are at http://www.freepascal.org/maillist.var
You will find more informations about FPC at http://www.freepascal.org/moreinfo.var
(I'm the author of the buildfaq document above)
There are some limitations. You can't target x86 from powerpc, because powerpc misses an "extended" type. But in generally it works.
I have generated a complete Lazarus for OS X on Windows.
I would virtualize Linux, as even if you can cross-compile, it means you're not testing the binaries on their native platforms. OS X is a trickier problem.
It is not possible to compile from one platform to another. We have a Mac and use FPC quite often. If you need some help with compiling on a mac, drop me a message.