RioTboard dead after reset

For something like this the more clues you can provide the better.  Kinda shooting in the dark here.

The two led's for a few seconds, going to one is what you should expect.  So I have to default to the first rule in tech support.  Check and double check all your connections and display settings.  Sounds like it should be working.

This is just a SWAG as I haven't studied the RIoTboard in detail, but with most Linux systems you must be careful how you turn them off.  Specifically, you must synchronize the file system or it may be in an inconsistent state when you turn the power off or press the reset button.  This is certainly true of Raspberry Pi.

If this is what happened, it's probably easiest to reload the operating system image.  To prevent it from happening again, see if there's a "shutdown" command in whatever OS you're using.  The usual Unix command is "shutdown -h now".  A GUI OS usually has a shutdown command somewhere in the menu system.

All the connections are ok, just the monitor and the plug. I have tested different options and no way.

Regarding the reset, I know that linux does not like to be shutdown or reset without doing the syncs, but there is no power-off button. If someone knows how to shutdown an android using the gui.

In any case, the board is still dead, or at least not presenting anything on the screen.

You could try to re-image it as johnbeetem suggested.  For info on how to do that check out page 42+ of the RIoTboard: User Manual for RIoTboard Platform

What did you have running when you reset?    I routinely pull the plug on mine every day and have not encountered this.  I did a little digging on the Android forums for soft power off' via adt commands but only found reboot (adt reboot) .   I do not see a way to do it from within the actual environment. Will keep looking.

Like John, I don't have a RIoTboard, so have no way to verify if what I say is useful..  That said, the RIoT is just another SBC and on the majority of them you really need a serial console connection to be able to see any error messages during the boot process. Whether those error messages are useful to you is a different discussion, but the fix could be quick and easy if you know what's wrong.

There seems to be a serial connection at J18, bottom of page 18 in the schematics.  Whether that's used as the debug console during boot I'm not sure, if it's not then it would seem you'd need to investigate the OpenSDA stuff on page 20 of the schematics as that's connected to the other uart.

Like Jose, I am also in the same boat. I just got my new RiotBoard, plugged the same connections in and nothing is appearing on my monitor. I plugged in a 5V power supply and see that 2 LED's light up, shortly after only 1 LED stays on and that eventually turns off. I have tried adjusting my screen resolution, tried using different monitors, tried the reset button and still nothing. I read somewhere about connecting to the DEBUG port itself but I am a noob to all this and don't have a cable to connect the debug port and I haven't used PUTTY in years. I've also tried searching for a Customer Care number to call RiotBoard but they don't seem to have any listed. Can some one help? Ask me questions, give me ideas, anything!! I just want to get this board working

Rick,

If all of the lights go out then I'd suggest looking at your power supply and whether it can supply enough current.  This may not be the cause though, if we assume that the board has actually booted into android then there's a timeout after which android will put the board to sleep.

Best bet is to get yourself a cable for the debug port as at least that way you'll be able to tell if the board boots at all.

On the monitor front, there's at least a couple of other posts on similar problems

http://www.element14.com/community/thread/32288/l/no-video-connection-with-android-image

http://www.element14.com/community/thread/31238/l/screen-resolution-with-preinstalled-android

most of the solutions you'll see in those discussions either require a different display, or a debug cable to change some settings.

Hey selsinork

Thanks for the quick reply. I have ordered a cable and I am just waiting for it to arrive. In the mean time, I have previously reviewed the posts you suggested and I will try them once the cable arrives. Are you able to provide me a walkthrough on how to actually connect the Riotboard to my computer to allow me to see the uBoot and whatever else I need to diagnose? I am not sure if PUTTY is the best, which COM port to use and how it works. FYI I ordered a USB debug cable. (USB to Serial Console Debug Cable for Raspberry Pi | eBay)

There's a reasonable explanation of how to use putty with the RIoT in this blog post http://www.element14.com/community/community/knode/single-board_computers/riotboard/blog/2014/02/25/impressions-with-the-riotboard-and-changings-its-operating-system-in-windows

Unfortunately there's no way for me to help you work out what COM port the cable will appear as on your computer. It depends on what other things you have plugged in.

A cable that works with the RPi shoule be fine with the RIoT, but as there's no connection details on that eBay page, it's difficult to know.  At a guess from the photo, the black wire is probably ground, red either 5v or 3.3v and should be left unconnected. Green and White probably TX & RX.  Some connection details here http://www.element14.com/community/message/106676/l/usb-to-ttl-connection#106676 but as you can see they both have cables with different coloured wires.

Get the console working first, then worry about solving the next problem

OK sounds good, once the cable arrives I will check to see if it is even booting and work my way from there. I will keep you posted. Thanks again!!