Got TC up and running in a minimal way on my Asus m004u ChromeBOX! My objective was to run natively from a usb boot, and NOT inside a chromeos chroot (crouton).
Mostly notes and a big gotcha' where smarter guys may want to take it follows:
As usual, it needs to be put into developer mode, and the usb boot enabled. I also had to reset the SEAbios. Details here:https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/asus-chromebox
So far so good. BUT due to a lack of my own knowledge on how to put a sysconfig together properly for the image, (despite the great faqs) AND a keyboard-bug during boot (chrome hardware issue, not tc's), the following may be amusing....
Burning the iso for usb boot:
Unfortunately, bmarkus' awesome usb burning utility doesn't detect my external pendrive.
We all know that 3rd-party burners, like unetbootin and other don't properly recognize the TC layout (or work at all), but I forged ahead.
Using RUFUS as the burner, this allowed for booting from the usb drives - BUT of course it does not know about the TC requirements. But at least I'm on the air so to speak - minimally.
KEYBOARD PROBLEM with boot!
When presented the boot option splash screens in sysconfig, none of the keys work! The only thing you can do is wait for the default timeout as your only option. Not tc's problem. Even an Acer chromebox keyboard did not work.
For reference: A Knoppix 7.7 usb stick provided to me also booted *eventually*, but at the boot splash screen where you can specify custom bootcodes / cheatcodes, the keyboard too was disabled. So one had to accept the defaults. But I want to run TC, not Knoppix.
Keeping in mind I'm not using a tc-specific layout burner, but a generic 3rd party Rufus utlity, here is what happens:
Tinycore images - all defaults just timeout and reboot the machine to dev mode.
Core images - YES! Still, no keyboards, but at least after the timeout, I'm up and running with a TC cli - and by then the keyboard *does* work.
Core 7.2 - boots after timeout no problem.
Core 8.0 - causes reboot
PureCore64-8.0 - boots after timeout no problem.
Smart guys will want to put together their own syslinux configuration, with all the options they want up front (since the non-functional keyboard during syslinux boot) to get up and running.
Until I get smarter, I'll just be putting persistence on another usb stick.