okay so im really really into the jaguarboard obviously was super excited to get mine, but its become apparent im having some real issues.. and i dont know if i have a bad board or something..
-I have flashed with both win32 and *nix64 firmwares distributed from uefi.zip package
-could not get windows 10 to boot on w32 firmware from DVD or flash disk prepared with rufus, win32diskimager, dd, universal usb installer, etc
-currently im on nix64 firmware and im trying pretty desperately to install anything at this point, im making some progress, on the w32 firmware often I wouldn't even SEE my boot device in the bios menu, i made a ubuntu usb shtick [sandisk bla bla], when i try to boot from it it just flashes blue then back to the bios boot screen at the same spot..
-i followed the guide to the letter on installing openelec on the jag and it actually booted up to the install gui which baffles me.. the ONLY thing that boots up is the fedora that comes preinstalled [NO idea where.. i have no microSD, only a 128gb usb chip for hopeful OS].
-input issues; when trying to login to the fedora 22 [yeck] install i found that every char is followed by something like o > ; or something like r o> ; o o>; t>; , the key here is to change input i guess, pressing superkey+F2 actually resolves this issue: HOWEVER this does not help that i cannot use the "+" within the bios to like change the date.
sorry if this is a big post but idk im at a loss, I cannot get any operating systems to boot.. basically whatsoever.. I mean lol I know a lot lot lot about machines and the board doesnt feel bad considering it actually boots a kernel [only elec and fedora for some goddamned reason tho]
ideas anyone?

If you can boot fedora and openelec, that means the hardware is fine. The problem is the way you created USB bootable drive, i think you did not create the right usb disk. a64 firmware is for 64 bit linux only and w32 firmware is for win8.1/win10 32bit system only!

And you must create UEFI bootable drive, not legacy bios bootable.

I hope my hardware is fine!
I do understand, a64 is linux64 and w32 is for win32 [I'd hope that should be obvious ]
but like I said I have tried [all on a win7 64bit machine] rufus, win32disk imager, universal usb installer [pendrivelinux.com methinks], and native dd on cygwin.. none of them worked for ubuntu64 16.04 [a64@jag] or windows32 10 [w32@jag]
-I belive some of the tools I was using was preparing the disk as Mbr, PERHAPS this is why my disk did not appear whatsoever in the bios, buut..?
-on rufus- is master boot record scheme for UEFI correct or should I use GPT?
I will make a damn small linux bootdisk and report back my findings
Thanks for the help!

okay- made a 8gb sandisk flash disk into a knoppix damn small linux flash disk with the dsl4.4.10.iso and rufus on my win7 machine.
-when I go to format the disk as "MBR partition scheme for UEFI" I see the same error message that occurs when I tried to make a few other disks for the jaguarboard mint and ubuntu i belive::
"Unsupported ISO;
when using UEFI type target, only EFI bootable iso images are supported, please select an EFI bootable ISO or set the target type to BIOS"
>ok
so What ive been using as the partition scheme is "mbr partition scheme for BIOS or UEFI-CSM"
no errors are reported by rufus, the disk boots fine in moba livecd emulator [to test the boot in a VM- great software-- freeware i believe actually] and I SEE my sandisk in the boot menu of the jag's bios however again, as soon as I try to boot it flashes me right back to the same menu.. cannot init.. somewhere like from the bios to the disk.
is this because of my partition scheme? and another point Ive only been using fat32 for the boot disk- even on a64 linux firmware..
erg :/

PROGRESS; i tried a new out of box flash disk and by the grace of god she boots ubuntu64 now actually into the grub prompt and up to the install point, but catches on a fairly common kernel issue "nmi watchdog soft lockup cpu#0&2 stuck for 22seconds [from systemd-udev:1338&1319]"
oddly enough ive run into this on ubuntu 16.04 and 14.04.. ill try a few more distros, mint elementaryos, some slack, and ill flash with the w32 firmware and test my win10x32 iso on this new disk.
-the only real prominent low-level issue i seem to have now is actually my bios isnt keeping the clock set after power down for like ~30 mins.. uhh no battery for the onboard clock? or something bad that's not supposed to be occurring?

Hi Sir,

The DSL or knoppix does not support UEFI, so they were failed to boot up, you need to use a ISO file with UEFI supportable.
When you create bootable disk, you must choose "MBR partition scheme for UEFI" !

Here is a Ubuntu 14.04.4 DD image, you can dd the img file into onboard flash, then you can boot the ubuntu up.
yunpan.cn/cBwCWNBbpIvxq
Access code: b9ba