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?
Daniel
PS 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- ;-) ?
How about pressing the S4 button on the board? It works for me for jumping into fastboot.
Z
On 28 September 2015 at 20:39, Daniel Thompson daniel.thompson@linaro.org wrote:
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?
Daniel
PS 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- ;-) ? _______________________________________________ Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
On 28 Sep 2015 19:45, "Zoltan Kuscsik" zoltan.kuscsik@linaro.org wrote:
How about pressing the S4 button on the board? It works for me for
jumping into fastboot.
Z
On 28 September 2015 at 20:39, Daniel Thompson daniel.thompson@linaro.org
wrote:
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?
Daniel
PS 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- ;-) ?
You should be able to use the Sonic Screwdriver 96boardsctl utility to reset the board. It twiddles the reset line on the LS connector, which is the same signal as Vol- (at least, so I'm told)
g.
Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
-- Zoltan Kuscsik
Senior Software Developer, Linaro Digital Home Group email: zoltan.kuscsik@linaro.org IRC: zoli_ on irc.linaro.org
Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
On 28/09/15 19:52, Grant Likely wrote:
PS 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- ;-) ?
You should be able to use the Sonic Screwdriver 96boardsctl utility to reset the board. It twiddles the reset line on the LS connector, which is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would explain why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
On 29 Sep 2015 11:20, "Daniel Thompson" daniel.thompson@linaro.org wrote:
On 28/09/15 19:52, Grant Likely wrote:
PS 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- ;-) ?
You should be able to use the Sonic Screwdriver 96boardsctl utility to reset the board. It twiddles the reset line on the LS connector, which is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would explain
why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can
physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence. The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
g.
On 29/09/15 12:03, Grant Likely wrote:
PS 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- ;-) ?
You should be able to use the Sonic Screwdriver 96boardsctl utility to reset the board. It twiddles the reset line on the LS connector, which is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would
explain why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can
physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence.
Wouldn't do any harm ;-)
The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
I've tried a fair few combinations.
Pressing and holding SW2 (aka screwdriver power pin) for 15 seconds causes the board to reset itself although, unlike a typical android phone, the board starts again automatically without any need for further presses of SW2. However I haven't (yet?) found any way to make SW4 influence the resulting reboot.
Daniel.
On Tue, 2015-09-29 at 12:32 +0100, Daniel Thompson wrote:
On 29/09/15 12:03, Grant Likely wrote:
PS 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- ;-) ?
You should be able to use the Sonic Screwdriver 96boardsctl utility to reset the board. It twiddles the reset line on the LS connector, which is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would
explain why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can
physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence.
Wouldn't do any harm ;-)
The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
I've tried a fair few combinations.
Pressing and holding SW2 (aka screwdriver power pin) for 15 seconds causes the board to reset itself although, unlike a typical android phone, the board starts again automatically without any need for further presses of SW2. However I haven't (yet?) found any way to make SW4 influence the resulting reboot.
It looks like there is no user-space daemon, which handle SW2 KEY_POWER event and power-off gracefully the system.
I think 15 seconds "de-bounce" interval is what is hard-coded in the PMIC itself, before it triggers hard-reset to the system.
Probably, not checked, LK, which implement fastboot control interface, don't start "fastboot" mode when hard-reset is detected.
Regards, Ivan
On Tue, Sep 29, 2015 at 9:42 AM, Ivan T. Ivanov iivanov.xz@gmail.com wrote:
On Tue, 2015-09-29 at 12:32 +0100, Daniel Thompson wrote:
On 29/09/15 12:03, Grant Likely wrote:
> PS > 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- ;-) ?
You should be able to use the Sonic Screwdriver 96boardsctl utility to reset the board. It twiddles the reset line on the LS connector, which is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would
explain why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can
physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence.
Wouldn't do any harm ;-)
The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
I've tried a fair few combinations.
Pressing and holding SW2 (aka screwdriver power pin) for 15 seconds causes the board to reset itself although, unlike a typical android phone, the board starts again automatically without any need for further presses of SW2. However I haven't (yet?) found any way to make SW4 influence the resulting reboot.
It looks like there is no user-space daemon, which handle SW2 KEY_POWER event and power-off gracefully the system.
IIRC, handling KEY_POWER will work with a GUI running, but for headless you would need acpid running.
Rob
Op 30 sep. 2015, om 00:37 heeft Rob Herring rob.herring@linaro.org het volgende geschreven:
On Tue, Sep 29, 2015 at 9:42 AM, Ivan T. Ivanov iivanov.xz@gmail.com wrote:
On Tue, 2015-09-29 at 12:32 +0100, Daniel Thompson wrote:
On 29/09/15 12:03, Grant Likely wrote:
>> PS >> 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- ;-) ?
You should be able to use the Sonic Screwdriver 96boardsctl utility to reset the board. It twiddles the reset line on the LS connector, which is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would
explain why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can
physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence.
Wouldn't do any harm ;-)
The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
I've tried a fair few combinations.
Pressing and holding SW2 (aka screwdriver power pin) for 15 seconds causes the board to reset itself although, unlike a typical android phone, the board starts again automatically without any need for further presses of SW2. However I haven't (yet?) found any way to make SW4 influence the resulting reboot.
It looks like there is no user-space daemon, which handle SW2 KEY_POWER event and power-off gracefully the system.
IIRC, handling KEY_POWER will work with a GUI running, but for headless you would need acpid running.
No need for acpid If your SoC matches this udev rule: https://github.com/systemd/systemd/blob/master/src/login/70-power-switch.rul... , systemd will catch the event and do a shutdown.
regards,
Koen
On Wed, 2015-09-30 at 06:48 +0200, Koen Kooi wrote:
Op 30 sep. 2015, om 00:37 heeft Rob Herring herring@linaro.org> het volgende geschreven:
On Tue, Sep 29, 2015 at 9:42 AM, Ivan T. Ivanov xz@gmail.com> wrote:
On Tue, 2015-09-29 at 12:32 +0100, Daniel Thompson wrote:
On 29/09/15 12:03, Grant Likely wrote:
> > > PS > > > 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- ;-) ? > > You should be able to use the Sonic Screwdriver 96boardsctl utility to > reset the board. It twiddles the reset line on the LS connector, which > is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would
explain why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can
physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence.
Wouldn't do any harm ;-)
The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
I've tried a fair few combinations.
Pressing and holding SW2 (aka screwdriver power pin) for 15 seconds causes the board to reset itself although, unlike a typical android phone, the board starts again automatically without any need for further presses of SW2. However I haven't (yet?) found any way to make SW4 influence the resulting reboot.
It looks like there is no user-space daemon, which handle SW2 KEY_POWER event and power-off gracefully the system.
IIRC, handling KEY_POWER will work with a GUI running, but for headless you would need acpid running.
No need for acpid If your SoC matches this udev rule: https://github.com/systemd/systemd/blob/master/src/login/70-power-switch.rul... , systemd will catch the event and do a shutdown.
Well, fix in gpio-keys is pretty new addition :-) [1]
Regards, Ivan
[1] https://github.com/systemd/systemd/commit/fc4049c1ab59b4d5460fc6c2076d086a16...
On Tue, Sep 29, 2015 at 11:48 PM, Koen Kooi koen.kooi@linaro.org wrote:
Op 30 sep. 2015, om 00:37 heeft Rob Herring rob.herring@linaro.org het volgende geschreven:
On Tue, Sep 29, 2015 at 9:42 AM, Ivan T. Ivanov iivanov.xz@gmail.com wrote:
On Tue, 2015-09-29 at 12:32 +0100, Daniel Thompson wrote:
On 29/09/15 12:03, Grant Likely wrote:
>>> PS >>> 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- ;-) ? > > You should be able to use the Sonic Screwdriver 96boardsctl utility to > reset the board. It twiddles the reset line on the LS connector, which > is the same signal as Vol- (at least, so I'm told)
Ah... Reset == Vol-Down. I didn't think if that (Esla: that would
explain why the reset button on the Sonic Screwdriver didn't do what we were expecting).
Anyhow the trick works.
That said, rather frustratingly the trick only works when I can
physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence.
Wouldn't do any harm ;-)
The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
I've tried a fair few combinations.
Pressing and holding SW2 (aka screwdriver power pin) for 15 seconds causes the board to reset itself although, unlike a typical android phone, the board starts again automatically without any need for further presses of SW2. However I haven't (yet?) found any way to make SW4 influence the resulting reboot.
It looks like there is no user-space daemon, which handle SW2 KEY_POWER event and power-off gracefully the system.
IIRC, handling KEY_POWER will work with a GUI running, but for headless you would need acpid running.
No need for acpid If your SoC matches this udev rule: https://github.com/systemd/systemd/blob/master/src/login/70-power-switch.rul... , systemd will catch the event and do a shutdown.
I should have known systemd has consumed this function as well.
Rob
On Wed, Sep 30, 2015 at 5:22 PM, Rob Herring rob.herring@linaro.org wrote:
On Tue, Sep 29, 2015 at 11:48 PM, Koen Kooi koen.kooi@linaro.org wrote:
Op 30 sep. 2015, om 00:37 heeft Rob Herring rob.herring@linaro.org het volgende geschreven:
On Tue, Sep 29, 2015 at 9:42 AM, Ivan T. Ivanov iivanov.xz@gmail.com wrote:
On Tue, 2015-09-29 at 12:32 +0100, Daniel Thompson wrote:
On 29/09/15 12:03, Grant Likely wrote:
>>>> PS >>>> 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- ;-) ? >> >> You should be able to use the Sonic Screwdriver 96boardsctl utility to >> reset the board. It twiddles the reset line on the LS connector, which >> is the same signal as Vol- (at least, so I'm told) > > > Ah... Reset == Vol-Down. I didn't think if that (Esla: that would explain why the reset button on the Sonic Screwdriver didn't do what we were expecting). > > Anyhow the trick works. > > That said, rather frustratingly the trick only works when I can physically un/plug the power to the main board (if I use the 'screwdriver to simulate a long press off SW2 the board doesn't revisit fastboot properly).
I think we need some help from our Qualcomm friends here on a reset sequence.
Wouldn't do any harm ;-)
The 'screwdriver has access to the power and reset button signals, and I can make them be twiddle in whatever order is required.
Does perhaps Vol- need to be held down before pressing power?
I've tried a fair few combinations.
Pressing and holding SW2 (aka screwdriver power pin) for 15 seconds causes the board to reset itself although, unlike a typical android phone, the board starts again automatically without any need for further presses of SW2. However I haven't (yet?) found any way to make SW4 influence the resulting reboot.
It looks like there is no user-space daemon, which handle SW2 KEY_POWER event and power-off gracefully the system.
IIRC, handling KEY_POWER will work with a GUI running, but for headless you would need acpid running.
No need for acpid If your SoC matches this udev rule: https://github.com/systemd/systemd/blob/master/src/login/70-power-switch.rul... , systemd will catch the event and do a shutdown.
I should have known systemd has consumed this function as well.
well, you can also assume that if it hasn't yet, then it will soon ;-)
On 30 September 2015 at 18:22, Rob Herring rob.herring@linaro.org wrote:
On Tue, Sep 29, 2015 at 11:48 PM, Koen Kooi koen.kooi@linaro.org wrote:
No need for acpid If your SoC matches this udev rule: https://github.com/systemd/systemd/blob/master/src/login/70-power-switch.rul... , systemd will catch the event and do a shutdown.
I should have known systemd has consumed this function as well.
will you miss acpid? ;)
Anyways looks like we got another reason to backport a newer systemd/udev to our jessie based images.
Riku
On 28/09/15 19:44, Zoltan Kuscsik wrote:
How about pressing the S4 button on the board? It works for me for jumping into fastboot.
That works for me too. Unfortunately once the sensor board is installed the button is no longer easily accessible...
Daniel.
Z
On 28 September 2015 at 20:39, Daniel Thompson <daniel.thompson@linaro.org mailto:daniel.thompson@linaro.org> wrote:
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? Daniel PS 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- ;-) ? _______________________________________________ Dev mailing list Dev@lists.96boards.org <mailto:Dev@lists.96boards.org> https://lists.96boards.org/mailman/listinfo/dev-- Zoltan Kuscsik
Senior Software Developer, Linaro Digital Home Group email: zoltan.kuscsik@linaro.org mailto:zoltan.kuscsik@linaro.org IRC: zoli_ on irc.linaro.org http://irc.linaro.org/
Le 28 sept. 2015 2:39 PM, "Daniel Thompson" daniel.thompson@linaro.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:
http://builds.96boards.org/snapshots/dragonboard410c/linaro/ubuntu/101/
It is the RC build...but testing isn't finished yet..
Daniel
PS 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 Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
-
Daniel Thompson -
Grant Likely -
Ivan T. Ivanov -
Koen Kooi -
Nicolas Dechesne -
Riku Voipio -
Rob Herring -
Zoltan Kuscsik