We tried to create a snappy for freedomotic. It works (with some issues) on Raspberry but it isn't installed on Ubuntu image. The repo (with some instructions) is available at https://github.com/freedomotic/fd-snappy
tried the udoo-snappy.img on 4GB SD card formatted as FAT32 or ext3. Neither worked on my Udoo dual. No screen output, any suggestions?
I tested only on udoo quad. Not sure if there is any video output. Probably only ssh. Try to connect serial console and check if you see something on it.
Tried using minicom on /dev/ttyUSB0 on CN6 with no results. dmesg shows that the connection is correct: 1738.709954] usb 1-1.4: Product: CP2104 USB to UART Bridge Controller [ 1738.709956] usb 1-1.4: Manufacturer: Silicon Labs [ 1738.709958] usb 1-1.4: SerialNumber: 0079156B [ 1738.710745] cp210x 1-1.4:1.0: cp210x converter detected [ 1738.783426] usb 1-1.4: reset full-speed USB device number 31 using ehci-pci [ 1738.876408] usb 1-1.4: cp210x converter now attached to ttyUSB0
The SD card has 4 partitions, first is Fat32 but not readable. the other three are ext4 with two systems installed as it should be. 1 4194kB 71.3MB 67.1MB primary fat32 boot, lba 2 71.3MB 1145MB 1074MB primary ext4 3 1145MB 2219MB 1074MB primary ext4 4 2219MB 3000MB 781MB primary ext4
I just downloaded version 2, unpacked, written with win32diskimager and after it was written I saw first partition and files on it. Try to download file again. Md5sum is a1620841c4726e278c4400eee35d4faf.
Then I'm not sure what is wrong. At least you should see first partition on SD card. To boot on dual... can't say if works or not.
According to Robert Nelson, from Digi-Key; "The current version of u-boot doesn't support SPL mode for the UDOO's this is why the current image from ubuntu only works on the QUAD. 2 options, Contact ubuntu directly and get them to build a DUAL variant Or use my u-boot patch, build your own version of u-boot and write it over the QUAD's image PS, I'm not sure what u-boot patches they use, so you might have to tweak the boot scripts."
U-boot in my snappy image is the same as used for OpenELEC. Which is u-boot 2013.10-rc4 + udoo support from U-Boot_Unico-2013 as patch. I don't know why are you mentioning image from ubuntu? Which image exactly are you using? And yes I'm building only for quad. And yes, there is no SPL from my informations. That's why there must be two different bootloaders. Update: Actually I'm using u-boot 2015.01. Just checked.
To test if you want. snappy-udoo-dl.img.gz https://drive.google.com/folderview...2NS1xRU1HTWl5SzU1cXpHcGFId3c&usp=sharing#list
I got u-boot messages on HDMI output which stopped at "mmc0: Timeout waiting for hardware interrupt" It set up the hdmi interface and usb keyboard and mouse. The SD card has the standard 4 partitions system-boot system-a system-b and writable.
So now it seems that it boots? Do you have connected serial console? Maybe there is something interesting. If you want you can compile image yourself from file archive-snappy.tgz. I have only udoo quad where v2 image was running fine.
since mmc0 refers to the micro SD card and I have formated and written the img file several times with the same results, it may be the micro SD card. The same results on the serial port as on the HDMI port.
I tried a new 16GB microSD card with the same results. I have attached the minicom capture file from the usb port to help in debugging.
Then I don't know what can be. In previous attempt you could see that quad device tree was used. But now I changed that but something else is still wrong. Can't help anymore. Seems some kernel issue or error in device tree. Have only quad board.
