From drivers, to FAQs to user guides. Find everything you need to make the most out of Mojo here.
Frequently Asked Questions
Click on the FAQ to view the answer to each question.
For Mac OS X 10.5 or higher. Mac OS X Tiger (10.4) users should download Mojo 3.3.3. It requires iTunes 6.0 or higher.What devices are compatible with Mojo?
- Mac Talent Mojo is a leading HR & Placement company providing effective Recruitment Solutions. This is our basic strength and we work with many corporate providing them with recruitment solutions.
- For Mac OS X 10.5 or higher. Mac OS X Tiger (10.4) users should download Mojo 3.3.3. It requires iTunes 6.0 or higher.
Once purchased, you simply need to connect the USB to Micro USB cable to Mojo. Your iDevice will automatically recognise Mojo and will instantly play music through the device.
You can check whether your Android device is USB OTG compatible by referring to your manufacturers instruction manual. Once you have done this please download an high-resolution music player, such as USB Audio Player Pro or Onkyo Music Player, to work with Mojo.
Its worth noting that sometimes you are required to unlock the USB audio output function, so if you are not getting audio please refer to the settings page and make sure that the USB audio out function is enabled.
We are currently compiling a list of natively supported devices, so check back to confirm whether your device is supported.
If all of the above solutions are unsuccessful then please try a different USB lead. If you are using a poor quality USB lead or a lead that is over 1.5m then Mojo may not function as intended.
Finally, if you are using a Windows computer then you will need to install the driver that we have provided above. If you are using your Mojo with an Android device then you will need to make sure that it is OTG (On The Go) compatible. Please refer to your device manufacturers specifications.
Windows Driver Download
if you're using a Windows PC, then you will need to download the driver and install it for Mojo to function.
Mojo Machine Learning
We’re here to help. Please click here to be taken to our parent website where you can complete our contact form.
What is this? These are instructions for getting the Xilinx tools up and running on OSX to work with the Embedded Micro Mojo v3 FPGA development board.
Why am I doing this? I bought the Mojo v3 development board last year to start playing with FPGA’s but haven’t gotten around to using it. I figured now is as good a time as any to start…
Why not just dual boot into Windows or Ubuntu? I don’t really have a Windows machine anymore, and why dual boot when I can just use a virtual machine?! I’ve been playing with Vagrant and Ansible at work, so I figured I’d try them out here. My goal is to automate most of the annoying things to get a Xilinx development board working on a VM so that you don’t have to. I was able to get almost everything automated, except for the Xilinx ISE installation, since it requires some user interaction :-/
- VirtualBox and VirtualBox extension pack
brew cask install virtualbox virtualbox-extension-pack
- or download from the VirtualBox website
brew install vagrant
brew install ansible
- Xilinx ISE WebPack for Linux Installation file
- Download from the Xilinx website (Make sure you get the “Full Installer for Linux”)
Install VirtualBox, vagrant, and ansible
Clone the osxMojo repo
git clone https://github.com/alvarop/osxMojo.git
If you already have it, copy your Xilinx.lic license key file to the roles/ise/files/ directory. This is for ISE WebPack, you can get a free one from the Xilinx license page. If you have trouble, keep going and ISE will ask you for one later on when it needs it.
In the top directory for the repo, run
- This will setup an ubuntu VM with most prerequisites as well as create shortcuts for things
This is what a successfull 'vagrant up' should end like
After vagrant up finishes running, login via the VirtualBox window with username vagrant and password vagrant
Once the desktop comes up click on “Use default config”
This is what the desktop should look like
On OSX, extract the Xilinx ISE Webpack installation files to the top directory on the host machine (For me it was Xilinx_ISE_DS_Lin_14.7_1015_1)
In the VM, open a terminal and run
sudo /vagrant/Xilinx_ISE_DS_Lin_14.7_1015_1/xsetup to install the Xilinx ISE tools
Run ISE installer as root
Only install the ISE Webpack
IMPORTANT: Make sure you set the installation path to /vagrant/opt/Xilinx
Make sure you set the installation path to /vagrant/opt/Xilinx
This part takes forever
Seriously... I wrote most of the post and this is still going.
Once the installation is complete, you should be able to run ISE from the desktop icon!
Mojo Maca Unleashed
Working with ISE
You can now open ISE with the included desktop shortcut
As an example, you can download the Mojo base project from Embedded Micro’s Creating a Project tutorial. I put the base project in a directory I created under osxMojo/projects/ on OSX. You can now open the project from ISE.
You can generate the FPGA programming file by double clicking “Generate Programming File” on the bottom left (If you can’t find it, check out the Embedded Micro tutorial. It’s much better than this.)
Programming the Mojo v3
First, you need to connect your mojo v3 to the computer via USB. Assuming everything goes as planned, the device should be mounted under /dev/ttyACM0. You can check easily by doing
ls -l /dev/ttyA* on the terminal.
Make sure the mojo is connected
You can launch the Mojo Loader from the desktop to get started.
Select the mojo serial port. (/dev/ttyACM0 in my case)
You can now open the mojo programming/binary file created by ISE by going to /vagrant/projects/mojo-base-project-master/syn/mojo_top.bin
Once the file is selected, you should be able to program the mojo by clicking on load!
If you’re not using ISE and want to save some memory, you can do
vagrant suspend on the command line to put the virtual machine to sleep.
If you want to save disk space, you are able to do
vagrant destroy and
vagrant up again later without needing to re-install ISE, since we installed it in the /vagrant/opt directory, which is on the shared folder and not in the VM itself.