Le 28 sept. 2015 2:39 PM, "Daniel Thompson" <firstname.lastname@example.org> a écrit :
> Hi Folks
> I'm just trying to kick the tyres of my sensors board. I'm using a dragonboard because that's the board I have "spare" to play with.
> I've tried to play "dumb" and follow only documented instructions... as a result I have a dragonboard flashed with the latest builds of the boot-and-rootfs from the releases directory.
> This build does not play nicely with the sensors board because /dev/ttyMSM1 does not exist. As a result I cannot use the UART0 pins on the LS connector to try and talk to the AVR (i.e. this is *not* the known issue that the AVR may have no bootloader).
> I haven't yet made much of a attempt to debug this (and won't until tomorrow at best). However... has anyone already overcome this problem?
The latest release was done in July ... And we didn't have the support for this board yet. We've worked on that at Connect, and it will be there in next release, later this week.
Can you try this build:
It is the RC build...but testing isn't finished yet..
> Does anyone have a canned command to deliberately corrupt the boot-and-rootfs so I can get the board to jump into fastboot (so I can try a snapshot) without having to take the sensors board of the top so I can press Vol- ;-) ?
Cat /dev/zero > /dev/disks/by-partlabel/boot
> Dev mailing list