Re-starting and then starting up PandaBoard ES

RISC OS 5.19 (04 May 2012 build)

Ctrl-Shift-F12, Ctrl-Break hang (no keyboard or mouse response) my PandaBoard ES when needing to do the all too frequent reset.

So the only options left for a reset are all PandaBoard users best friend the reset button or disconnecting/re-instating the power.

However this on my set up no longer works.

I use the HDMI connection into a Dell U3011 monitor.

In order for the above resets to work the monitor must be switched off or disconnected (otherwise you only get 1 LED lighting up on the motherboard and hence no boot).

This used to happen when I first got the PandaBoard in March then stopped with the custom ROMs built by Willi Theis and Chris Gransden.

It looks like it has somehow re-appeared with the recent merging of the OMAP3 and OMAP4 sources…

Sorry to resurrect an old thread, I have this exact same issue as Keith.

Does anyone else have this issue?

Yep. Happens to me every time. Have to unplug it and plug it back in.

Our (CJE) PandaBoard Power Control/RTC Module if used with a miniITX/ATX PSU includes a fix for this!

Was going to provide a link to it on our website but it isn’t there:-(

I’ll get that fixed a.s.a.p.

Just placed an order for a CJE RTC module!

This bug is now far more specific than my original post.

The issue is to do with PandaBoard start up when you either press S1 on the board (it is the pushbutton nearest the SD-Card slot) or use a pushbutton accross pin 26 (Power On Reset) and pins 27 or 28 on Expansion connector A (J3) to reset the board when it is running.

What should happen is that, if you keep an eye on the LEDs on the board, the board restarts as normal i.e. bothe LEDs light up and then, as RISC OS loads, go off and one of them then becomes a “hard drive” indicator.

What is actually happening is that only one LED comes on and the board stays like that. This error state is normally associated with the MLO not being properly processed.

So yes you can buy extra hardware to combat this but it would be much more preferable for the bug to be fixed…

Can somebody with a PandaLand SD-Card or an ARMiniX i.e. a set-up that has overlapping partitions (like a Raspberry Pi) on their SD-Card try this please?

Thanks in advance.

Pressing CTRL-Break causes the LED on the keyboard to go off (and thus no keyboard input).

Powering off and on again causes it start up again.

Typing CTRL-SHIFT-f12 then ENTER just leaves the keyboard LED off and a black screen.

This is tested with a debug RISC OS ROM dated 25-Feb-2013 and a Raspberry-Pi like SD card set up on a Pandaboard ES as shown below. Note not the latest HD4 image nor the latest ROM

BOOT.SCR

RISC OS PandaBoard boot script
fatload mmc 0:1 0x4030C000 cmos
fatload mmc 0:1 0x81000000 riscos
go 0x81000000

UENV.TXT

uenvcmd=fatload mmc 0:1 0x81000000 riscos;go 0x81000000

uenv_cmos.txt

uenvcmd=fatload mmc ${mmcdev} 4030C000 cmos;fatload mmc ${mmcdev} ${loadaddr} riscos;go ${loadaddr}

CONFIG.TXT:

#hdmi_mode=16
#arm_freq=800
hdmi_drive=2
disable_overscan=1
framebuffer_ignore_alpha=1
framebuffer_align=0x100000
init_emmc_clock=100000000
kernel=riscos.img

That wasn’t what was being asked for.

It is known that ctrl-break doesn’t yet work and the shutdown menu has been improved.

What we needed to know was what happened if S1 (or a pushbutton connected to the equivalent pins on expansion connector A (J3)) was pressed.

The question that was wanting to be answered was does the same thing happen if you have overlapping partitions.

It has now been tested and the answer is yes – the behaviour is the same.

Incidentally what does that Raspberry Pi configuration file have anything to do with a PandaBoard?

Sorry, wasn’t clear what was wanted. The SD card is (AFAICR) one that was able to boot on a Raspberry Pi, Beagleboard XM and Pandaboard ES (or at least two of them if not all three).

Can somebody with a PandaLand SD-Card or an ARMiniX i.e. a set-up that has overlapping partitions (like a Raspberry Pi) on their SD-Card try this please?

I have the SD card provided by R-Comp under the Pandaland scheme, and reset doesn’t work.
After a reset the Pandaboard only has 1 LED lit next to the SD card.

The SD card is the key!
If I use a SanDisk SD card the Pandaboard won’t work when I push the reset button.
(I get the single LED lit next to the card slot)

If I take an image of the SanDisk card and restore it to a Kingston card, the pandaboard then works when I push the reset button!
The Kingston card is an 8GB Class 6 card. (I’m not sure of the read/write speeds, but it’s nowhere near as quick as the SanDisk)

Perhaps the speed of the card used is the issue?

@Keith,

Is this post relevant? It includes reference to a hang after CTRL-SHIFT-f12 ENTER on a Raspberry Pi.

Rob Heaton is sort of right!

This is all to do with what type of SD-Card you are using not just the speed as can be seen below:

Sandisk Extreme Pro class 10 (95MB/s) – N
Sandisk Extreme class 10 (45MB/s) – N
Sandisk class 10 – Y
Lexar Professional class 10 (60MB/s) – Y
Kingston class 6 – Y
Dane-elec class 4 – Y

So why these extreme Sandisk cards have this I have no idea but at least we have got somewhere.

Please be aware that this only applies to the reset function of the pushbutton on the board. If you are running one of the commercial power supply interfaces or machines, you don’t really need to worry about this.

Also please be aware that crtl-break still doesn’t work.

The reboot issues with certain SD cards isn’t limited to RISC OS, both Ubuntu & Android exhibit the same behavior.
Does anyone know if this is likely to be caused by the first stage boot loader, MLO or u-boot?

Does anyone know if this is likely to be caused by the first stage boot loader, MLO or u-boot?

My understanding is that it is a bug in the x-loader when it initialises the sd card sub system after a reset making the card unreadable (so MLO does not even get loaded). Work around is either to turn off power or to remove/reinsert the SD card. Or find a brand of SD card that tolerates the problem and just works OK.

I have two different SD cards with the same image on them and one does reset correctly and the other hangs. Both do shutdown/restart and CTRL-Break correctly now.