I received my board today and tried to follow the guide to get started. However, I never get any output on the HDMI port - without or without the TF card inserted, and with any possible setting of the jumpers. I get a red light when I plug the device in. I get flashing lights on the ethernet sockets if I connect them, but nothing else.
Is my board broken or have I missed something? I don’t have USB serial connector to test that way.
Do you have any other SoC board with 3.3 v serial port (e.g. Raspberry Pi, …) that you could use instead of a USB to 3.3V TTL Serial UART cable to access the serial port on the VF2 ?
Even some Arduino boards could be configured as an Arduino Serial Bypass, which is effectively ignoring the Arduino chip altogether and using the on-board serial chip to function as a dumb USB to Serial Converter ( e.g. https://gist.github.com/wmhilton/6034455 ). But you would need to verify that the voltage was 3.3 volts for your particular make and model of Arduino to avoid any risk of permanently damaging the VF2.
I was in a similar situation before where I had no display and only the red led was on even though I followed the instructions. I don’t have a USB-serial connector as well. I did some digging and found that the sdcard.img on the VF2 SDK github repo tagged release works for me when flashed into an sd card, though you might need to change the boot mode before it can actually boot. If it works you should see a green led next to the red one that periodically flashes like a heartbeat.
That img should have mtd-utils installed, and also supports ssh, so if you know the ip address of your board you can ssh in as well as scp the relevant files from your PC to update spl and uboot.
Once I did this I was able to get a debian image running, but unfortunately what happened was a mouse cursor would display on my screen with a black background, and then proceeds to get stuck.
I can still ssh in to debian, though I’ve only just started playing around and haven’t figured out what’s wrong yet. Not sure why some people are able to get it working out of the box just like that but not ours. But hey, thats part of the fun!
You will only get a HDMI signal after booting from the TF card.
Did you try with Debian image version ending on 55?
Are you sure the HDMI cable is properly connected? At first it will go in relatively smoothly, but you need to use some “reasonable” force to get the HDMI cable in properly.
Yes I saw that post as well and just tried it out. It fixed my issue and I’m now getting a working display as well. Seems like I had the same situation as the author of the post where I had used a 4k monitor.
I updated the firmware (uboot and opensbi) and booted off the 69 debian image successfully. Everything is running, but I don’t have an image on my Aorus FI270Q monitor. I assume the 2560x1440 native resolution is the culpit. Anyway, here’s my modeset info:
Im in same boat as others with a no-boot situation with both 65 and 55… reading the instructions on how to update sp/uboot i have a couple of questions as the manual is not the clearest in the world:
for option 1, it says to wait for the command line uboot. Does that only work across serial port or should i see it on HDMI? And i assume no SD card installed.
For option 2, where are these commands run? On the board or a host PC its plugged into? i cant boot so cant do it on the board. I did install mtd-utils on a debian host, but it does not show anything when /proc/mtd is run from the directions. ( and flashcp isn’t part of the mtd-utils package )
I can try that, however the images i have now dont do squat, even for network. Instead of ‘the image on github’ is there an actual link to this magic image that boots enough to get network? ( to save me a bunch of searching )