Thanks for the quick reply, I do have a TTL 'RS232' connected and it works as a debug console, but the screen still boots in GUI, I am attempting to use QT with -qws without a windows manager, thus need to disable the GUI on bootup, and boot the LVDS screen in console mode.
I will follow up on the GPIO, Thanks
I'm trying to use my raspberrypi to open a putty serial connection with my riotboard. But it seems I've scrambled the riotboard's brains with my windows computers. It now gives me a grey screen where the android logo used to show up. Any backdoor resetting of hardware to at least make putty work?
Any backdoor resetting of hardware to at least make putty work?
THe RIoTBoard has no Backup Firmware or similar if you mean something like this.
It´s sort of like a PC. Just with a flash drive or SDCard instead of a HDD.
What you could do is connect it with a UART Serial cable and look what he´s giving you back on the console.
To reset it you have to Download the Android Image and write it onto the flash with the MFGTool.
You can Download both here: RIoTboard evaluation platform based on powerful multimedia application processor i.MX 6Solo
To find under Design Elements -> Software.
How do I use PuTTY to restore my Android Image on my RIoTboard? I'm using my Raspberry Pi...
You can´t restore it with putty or with your RaspberryPi.
You´ll need a PC with Windows and a USB to Mini USB Cable.
Everything is described here as tusharp already said: Impressions on the RIoTboard and changing its Operating System in Windows
It´s for putting Ubuntu Linux on it but you just have to use the Android Image instead.
The UART Serial connection is optional. It only shows you what actually happens while flashing the image.
There are ways in which a running linux image can be backed up. No idea if same can be done on android.
If you have not flashed any new image on SBC there are always ways to backup the original image.
mfgtools gives me an error code 21; each time i run it...
can you share the mfgtool.log file in the home folder of MFGTools.
Hi John. I have Riotboard up & running using the ubuntu 11.10 distribution and have got Python IDLE working through ssh tunneling and xwindows.
I am currently learning how to use the python pyo library as I am interested in audio programming.
I have audio working fine but am having trouble with MIDI. I have an M-Audio oxygen midi keyboard which I have plugged into one of the riotboards' USB ports and the aMIDI command sees the device and can read not on off messages, controller messages etc.... but when I try to use MIDI in the pyo library I get this error:
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
Portmidi warning: no midi device found!
I have tried using modprobe -a snd-seq and modprobe -a snd-MIDI but get a FATAL error message:
FATAL: Module snd_seq not found.
WARNING: Error running install command for snd_seq
Would you have any idea whats going on?
Also, if I wanted to update u-boot and compile and build and install debian as per Selsinorks' brilliant tutorials, could I do it using either just my riotboard or possibly using windows??
Thanks very much for your post and help.
All the best.
probably the particular alsa driver you need hasn't been built. The kernel used in the ubuntu image is fairly light on drivers, things that are not absolutely necessary tend to be missing.
Rebuilding u-boot/kernel on windows alone will be almost impossible. Normally what you'd do is to setup a linux virtual machine running on top of windows and use that.
It's certainly possible to build everything on the RIoTboard, I'd suggest you find a USB hard drive, real spinning rust variety, mount it somewhere and do all your compiling on the drive rather than on eMMC or SD-card. It'll give you a good performance gain. Even so, it will take quite some time, especially the kernel.
Also don't expect miracles going to Debian and new kernel, it's quite possible I've not included all of the Alsa drivers in the defconfig, but if you're compiling it anyway, then at least you get the chance to check and add any missing things that you need.
The other option is to recompile the 3.0.35 kernel you're using with ubuntu to include any missing drivers, radiatortwo described how to go about recompiling it here http://www.element14.com/community/message/110380/l/re-linux-where-is-uarts#110380
Keep watching the RIoTboard group - I hope to have a Debian image that you can write to an SD card (with win32diskimager or similar) fairly soon. It'll be very minimal to start, but will let you use apt-get / aptitude to install whatever you need from the main Debian repository.
Everyone's been super around here! Got my USB upload working to my RIoTboard!
Now PuTTY no longer works... It just sits there... No data.
Hi Selsinork. Spinning rust variety lol...
OK. I'm trying to build the Linux kernel and have been successful up to the point where I want to install the modules:
make modules_install INSTALL_MOD_PATH=output..........
When I try to do this I get this error:
ln: creating symbolic link `output/lib/modules/3.15.0-rc7/source': Operation not permitted
make: *** [_modinst_] Error 1
I'm not using a mechanical HDD but a 16GB sd card .
All worked well up till now..
Any ideas what might be going wrong??
Have you put the Boot Switches back to boot from eMMC?
It only shows nothing when it doesn´t find the boot image or when it´s in bootloader mode.