Can someone post the logfile from their serial during bootcycle so we can check the logfile.
Please list at same time exactly which file you downloaded from the wandboard download page.
Also to quickly confirm if a board is in working condition. You can read the startup guide. (top post on the forums). There is a way to connect the board over USB OTG and if the board pops up as a device you know that the board is operational and in working order.
Repost because no response on suggestions.
Looked through your boot log and, yes, looks clean to me too. Did notice the kernel bootline still specifies 1280x720@60. To get the 480p output do you interrupt the boot and set bootargs? I left my board in the office for the weekend. Nice find on the Boundary Devices link. I have the source respository in place and synced. Will get it set up for native compilation when I'm back in the office (with the mxc_hdmi.c CEA mods in place).
Hi folks. I need some help troubleshooting a WBQUAD issue: I'm not getting any video output from the HDMI out, and I'm not sure how to proceed. Note that I am not a developer, but I am a competent Linux user, so while a lot of things here will be over my head, I should be able to gather troubleshooting and debugging doc without much trouble.So far, I have . . .
- downloaded the WBQuad Android 4.2.2 image
- I've also walked through the following steps using the wandboard-quad-ubuntu-11.10-20130604.img image with the same results
DD'd that image to my mSD card per the Quick Start Guide: dd if=./android-4.2.2-wand-quad-preview-20130607.img of=/dev/[my_SD_card] bs=1M
- I've DD'd the image both from Linux and OSX machines with the same results
inserted that mSD card into the OS mSD card slot on the processor board, plugged in an HDMI-to-DVI cable that's attached to an HDCP-enabled monitor, and plugged in my 5V 2A 10W power supply
- I've tried this with multiple monitors and multiple HDMI-to-DVI cables with the same results
- I've tried booting with a USB keyboard attached, and/or with an OTG cable attached, with the same results
in every iteration above, a green light on the board comes on and nothing happens at the monitor
However, at least with Android, the image appears to be booting: with an OTG cable plugged between the board and my laptop, I can do the following:
- to reiterate, this is the same result whether booting the Android or Ubuntu images from the Wandboard downloads page
If I leave logcat running indefinitely, I eventually get kicked out of the shell and the board disappears from "adb devices".
- "adb devices" and see the board listed
- "adb shell" and get into a functional Android command prompt
- "logcat" from within the adb shell and watch as the boot progresses and generates log entriesI've also noticed that I can only access the device via adb on the first boot after DD'ing an image to the mSD card: the board does not appear in "adb devices" after any subsequent boot of the same mSD card (reset button, reboot from within the adb shell, hard power off/power on, etc.).So, I appear to have a functional board with a functional Android image on the mSD card, but I'm not getting any video output via HDMI, and the instability between first and subsequent boots isn't encouraging. Any advice on where to start?Note that I don't have a null modem cable available, but will be able to pick one up over the weekend to help with debugging.--Matt