No HDMI Signal - is my board dead?

Nurb432 · January 8, 2023, 8:45pm

Nope. solid red only. Never even blinks green like it tried and failed. No light for Ethernet. even if it never got to negotiation id at least expect to see a connection light.

Currently the switches are back to flash. ( after i tried the others, i put it back )

Written with etcher on Debian Linux, etcher verified, and is mountable on my host. This is also the 2nd card. My first attempt when i first got the board i used a different one, and intentionally switched for this round just in case ( forgot to mention that ) ( this isn’t my first rodeo, so i have hit every possibility i could think of before i asked for help )

I did forget to mention i used 2 different power supplies. 1 PD compliant, the other not.

First go around when i got the board i didnt yet have fan, but at your suggestion i removed it and tried again, and let it sit for ~10 minutes. Still nothing other than that damned angry red power led. ( its the fan off my v1 board, so it should have been ok anyway, but its unplugged for now. )

So frustrating, as it should not be this hard to get a little life out of it.

EDIT: after letting it run a bit longer i could feel the CPU was warm. Not hot, but warm enough to know it was warm. Donno if that means anything or not, just putting it out there.

tommythorn · January 9, 2023, 2:15am

I recommend you get a USB serial adapter and use that to troubleshoot - it’s really the lowest level. Not getting HDMI output is very much at the other end, eg. I have everything working except HDMI output.

Nurb432 · January 9, 2023, 12:07pm

As mentioned, i’m waiting on a new debug cable to arrive. I wasn’t able to find the one i had so had to order another.

Nurb432 · January 16, 2023, 6:29pm

Cable arrived. Switched back to sdcard.img, but nothing on debug output either. So i’m pretty much dead in the water. No green light, no debug output. ( ya i tried swapping the data cables in case they were mislabeled )

Other than waiting for new images and hoping they somehow magically wake this thing up, any other suggestions?

tommythorn · January 16, 2023, 11:21pm

If you are seeing no traffic on the serial connection (@ 115200 bps) then you have a serious problem. Things I would triple check: power supply (2 A at least) and serial USB connection. Try unplugging EVERYTHING except serial connection and power. Even without an SDcard, you should see the boot loaders messages on the serial connection.

Nurb432 · January 16, 2023, 11:54pm

That was my thought too. i should see * something *

I did test the cable with another board i had, slower, so it was not a bad cable but i did order a 2nd, that clearly says it can do 2mb. This one, while the chip is rated for 2mb it dint actually state a speed. If that dont work, i think im just screwed.

Michael.Zhu · January 17, 2023, 7:56am

@Nurb432 could you share the location of boot switch, the factory default is as below shown

and insert the sdcard.img TF card, power-up. it should be output something(serial port) and green light blinking.

note: the voltage of serial debug dongle should be 3.3v

Nurb432 · January 17, 2023, 12:17pm

Yes, i have restored it back to factory ( per advice somewhere else in this thread ).

I dont ever get a green light. The board never gets that far, it remains red no matter what settings i have or what image i use. ( or no image )

kesmik · January 17, 2023, 1:34pm

If you switch both switches to 0 (right as in picture above) it should try to boot and print something
If you switch bot switches to 1 (left as in picture above) it should enter y-modem mode and print CCCCCCCCCCCCCCCCCCCCCCCCC.

If you canot get any log to to serial there should be something serious IMO…

Just doublecheck if serial adapter is working by connect TX and RX. You should get same resposnes as you type.
And also make sure that they are correctly connected to your board TX/RX and GND, maybe you can post images of our setup

Nurb432 · January 17, 2023, 1:47pm

I think i posted this so sorry if its a repeat:

Trying for serial port: Nothing plugged in, no fan, no emmc, no m.2, no Ethernet, no HDMI

Swapped rx/tx in case the cable was mis-labeled
Cable verified on a random older ARM board i have.
3 different power supplies, 2 PD compliant, one not. All 30 watt or higher.
Tried ALL combinations of the switch. With SD and without, both the sdimage and 55 image. Even tried 69 image even tho it should not have worked until the update, but was desperate.
went back to default switch settings after a comment from one of the official people to leave it there.
with any combination, I never get a green light. Even for a blip
with any combination i do not get any activity on serial port.
Followed directions and used port 6,8,10 and correct baud.

kesmik · January 17, 2023, 2:02pm

Ech, do not know what else to suggest, because board should do something… It seems like a broken one… I have powered mine with Samsung charger any issues…

Correclty working board outputs such messages when alive.
BOOT SW 11:

(C)StarFive
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

BOOT SW 01 or 10

BOOT fail,Error is 0xffffffff
dwmci_s: Response Timeout.
BOOT fail,Error is 0xffffffff
dwmci_s: Response Timeout.
BOOT fail,Error is 0xffffffff

BOOT SWITCH 00

U-Boot SPL 2021.10 (Jan 08 2023 - 18:04:54 +0800)
DDR version: dc2e84f0.
Trying to boot from SPI

OpenSBI v1.0

EDIT: Just in case added serial connection screenshot.
I Think you have set everything correctly, but the board is broken…
P.S. green led blinks only then OS is alive, it is ot blinking in bootloader (anyway it looks like nothing is alive in your board)

Nurb432 · January 17, 2023, 2:04pm

That is my fear too, its toast. I figured regardless of switch or image i should at least see something on debug… and get a green light …

Unsure what my options will be at this point. its been here a month. ( was one of the super early bird supporters )

Admin · January 18, 2023, 2:33am

Hi Nurb432, we will contact you about the board problem.

linus.xu · January 18, 2023, 3:15am

Hi Nurb432,BOOT SWITCH 00, normal start, Debug uart Enter the following information, Please provide your VF2 startup log, analyze the cause.
U-Boot SPL 2021.10 (Dec 25 2022 - 20:59:18 +0800)
DDR version: dc2e84f0.
Trying to boot from SPI

OpenSBI v1.0

/ __ \ / | _ _ |
| | | | __ ___ _ __ | ( | |) || |
| | | | '_ \ / _ \ '_ \ ___ | _ < | |
| || | |) | __/ | | |) | |) || |
_/| ./ _|| ||/|____/|
| |
|_|

Platform Name : StarFive VisionFive V2
Platform Features : medeleg
Platform HART Count : 5
Platform IPI Device : aclint-mswi
Platform Timer Device : aclint-mtimer @ 4000000Hz
Platform Console Device : uart8250
Platform HSM Device : —
Platform Reboot Device : —
Platform Shutdown Device : —
Firmware Base : 0x40000000
Firmware Size : 360 KB
Runtime SBI Version : 0.3

Domain0 Name : root
Domain0 Boot HART : 1
Domain0 HARTs : 0*,1*,2*,3*,4*
Domain0 Region00 : 0x0000000002000000-0x000000000200ffff (I)
Domain0 Region01 : 0x0000000040000000-0x000000004007ffff ()
Domain0 Region02 : 0x0000000000000000-0xffffffffffffffff (R,W,X)
Domain0 Next Address : 0x0000000040200000
Domain0 Next Arg1 : 0x0000000042200000
Domain0 Next Mode : S-mode
Domain0 SysReset : yes

Boot HART ID : 1
Boot HART Domain : root
Boot HART Priv Version : v1.11
Boot HART Base ISA : rv64imafdcbx
Boot HART ISA Extensions : none
Boot HART PMP Count : 8
Boot HART PMP Granularity : 4096
Boot HART PMP Address Bits: 34
Boot HART MHPM Count : 2
Boot HART MIDELEG : 0x0000000000000222
Boot HART MEDELEG : 0x000000000000b109

U-Boot 2021.10 (Dec 25 2022 - 20:59:18 +0800), Build: jenkins-github_visionfive2-4

CPU: rv64imacu
Model: StarFive VisionFive V2
DRAM: 4 GiB
MMC: sdio0@16010000: 0, sdio1@16020000: 1
Loading Environment from SPIFlash… SF: Detected gd25lq128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

StarFive EEPROM format v2

--------EEPROM INFO--------
Vendor : StarFive Technology Co., Ltd.
Product full SN: VF7110A1-2239-D004E000-00000001
data version: 0x2
PCB revision: 0xb1
BOM revision: A
Ethernet MAC0 address: 6c:cf:39:6c22
Ethernet MAC1 address: 6c:cf:39:7c:ae:33
--------EEPROM INFO--------

In: serial@10000000
Out: serial@10000000
Err: serial@10000000
Model: StarFive VisionFive V2
Net: eth0: ethernet@16030000, eth1: ethernet@16040000
switch to partitions #0, OK
mmc1 is current device
found device 1
bootmode flash device 1
Can’t set block device
Failed to load ‘/boot/uEnv.txt’
Hit any key to stop autoboot: 0
Can’t set block device
Importing environment from mmc1 …

Warning: Input data exceeds 1048576 bytes - truncated

Info: input data size = 1048578 = 0x100002

385 bytes read in 3 ms (125 KiB/s)

Warning: defaulting to text format

Error: “boot2” not defined

47546 bytes read in 8 ms (5.7 MiB/s)
47546 bytes written in 15 ms (3 MiB/s)
Retrieving file: /boot/extlinux/extlinux.conf
823 bytes read in 5 ms (160.2 KiB/s)
U-Boot menu
1: Debian GNU/Linux bookworm/sid 5.15.0-starfive
2: Debian GNU/Linux bookworm/sid 5.15.0-starfive (rescue target)
Enter choice: 1
1: Debian GNU/Linux bookworm/sid 5.15.0-starfive
Retrieving file: /boot/initrd.img-5.15.0-starfive
9684953 bytes read in 412 ms (22.4 MiB/s)
Retrieving file: /boot/vmlinuz-5.15.0-starfive
8015200 bytes read in 341 ms (22.4 MiB/s)
append: root=/dev/mmcblk1p3 rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0
Retrieving file: /boot/dtbs/starfive/jh7110-visionfive-v2.dtb
47546 bytes read in 8 ms (5.7 MiB/s)
Uncompressing Kernel Image
Moving Image from 0x44000000 to 0x40200000, end=41767000

Flattened Device Tree blob at 48000000

Booting using the fdt blob at 0x48000000
Using Device Tree in place at 0000000048000000, end 000000004800e9b9

Starting kernel …

clk u5_dw_i2c_clk_core already disabled
clk u5_dw_i2c_clk_apb already disabled
[ 0.000000] Linux version 5.15.0-starfive (sw_buildbot@mdcsw02) (riscv64-unknown-linux-gnu-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP Mon Dec 19 07:56:37 EST 2022
[ 0.000000] OF: fdt: Ignoring memory range 0x40000000 - 0x40200000
[ 0.000000] Machine model: StarFive VisionFive V2
[ 0.000000] earlycon: uart0 at MMIO32 0x0000000010000000 (options ‘115200’)
[ 0.000000] printk: bootconsole [uart0] enabled
[ 0.000000] efi: UEFI not found.
[ 0.000000] Reserved memory: created CMA memory pool at 0x0000000080000000, size 512 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] Zone ranges:
[ 0.000000] DMA32 [mem 0x0000000040200000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x000000023fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040200000-0x00000000c010ffff]
[ 0.000000] node 0: [mem 0x00000000c0110000-0x00000000c01fffff]
[ 0.000000] node 0: [mem 0x00000000c0200000-0x000000023fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040200000-0x000000023fffffff]
[ 0.000000] SBI specification v0.3 detected
[ 0.000000] SBI implementation ID=0x1 Version=0x10000
[ 0.000000] SBI TIME extension detected
[ 0.000000] SBI IPI extension detected
[ 0.000000] SBI RFENCE extension detected
[ 0.000000] SBI v0.2 HSM extension detected
[ 0.000000] CPU with hartid=0 is not available
[ 0.000000] CPU with hartid=0 is not available
[ 0.000000] riscv: ISA extensions acdfim
[ 0.000000] riscv: ELF capabilities acdfim
[ 0.000000] percpu: Embedded 17 pages/cpu s31528 r8192 d29912 u69632
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 2067975
[ 0.000000] Kernel command line: root=/dev/mmcblk1p3 rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0
[ 0.000000] Unknown command line parameters: stmmaceth=chain_mode:1 selinux=0
[ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] software IO TLB: mapped [mem 0x00000000fbfff000-0x00000000fffff000] (64MB)
[ 0.000000] Memory: 7582168K/8386560K available (9884K kernel code, 4982K rwdata, 4096K rodata, 2191K init, 401K bss, 280104K reserved, 524288K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.000000] rcu: RCU debug extended QS entry/exit.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] CPU with hartid=0 is not available
[ 0.000000] riscv-intc: unable to find hart id for /cpus/cpu@0/interrupt-controller
[ 0.000000] riscv-intc: 64 local interrupts mapped
[ 0.000000] plic: plic@c000000: mapped 136 interrupts with 4 handlers for 9 contexts.
[ 0.000000] random: get_random_bytes called from start_kernel+0x4d0/0x6e2 with crng_init=0
[ 0.000000] riscv_timer_init_dt: Registering clocksource cpuid [0] hartid [1]
[ 0.000000] clocksource: riscv_clocksource: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 881590404240 ns
[ 0.000001] sched_clock: 64 bits at 4MHz, resolution 250ns, wraps every 2199023255500ns
[ 0.009003] clocksource: timer@13050000.ch0: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.020327] clocksource: timer@13050000.ch1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.031659] clocksource: timer@13050000.ch2: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.042985] clocksource: timer@13050000.ch3: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.054473] Console: colour dummy device 80x25
[ 0.060660] printk: console [tty0] enabled
[ 0.065214] Calibrating delay loop (skipped), value calculated using timer frequency… 8.00 BogoMIPS (lpj=40000)
[ 0.076437] pid_max: default: 32768 minimum: 301
[ 0.081751] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.090270] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.100565] ASID allocator disabled
[ 0.104504] rcu: Hierarchical SRCU implementation.
[ 0.109960] EFI services will not be available.
[ 0.115352] smp: Bringing up secondary CPUs …
[ 0.122016] smp: Brought up 1 node, 4 CPUs
[ 0.128480] devtmpfs: initialized
[ 0.139695] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.150559] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.171858] pinctrl core: initialized pinctrl subsystem
[ 0.178512] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.185729] cpuidle: using governor menu
[ 0.212031] platform soc:dsi-output: Fixing up cyclic dependency with 29400000.dc8200
[ 0.221212] platform 295d0000.mipi: Fixing up cyclic dependency with soc:dsi-output
[ 0.230052] platform 29590000.hdmi: Fixing up cyclic dependency with 29400000.dc8200
[ 0.250538] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.257922] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.268511] vgaarb: loaded
[ 0.271741] SCSI subsystem initialized
[ 0.276290] usbcore: registered new interface driver usbfs
[ 0.282365] usbcore: registered new interface driver hub
[ 0.288256] usbcore: registered new device driver usb
[ 0.294099] mc: Linux media interface: v0.10
[ 0.298846] videodev: Linux video capture interface: v2.00
[ 0.305072] Advanced Linux Sound Architecture Driver Initialized.
[ 0.312169] Bluetooth: Core ver 2.22
[ 0.316132] NET: Registered PF_BLUETOOTH protocol family
[ 0.321989] Bluetooth: HCI device and connection manager initialized
[ 0.328987] Bluetooth: HCI socket layer initialized
[ 0.334369] Bluetooth: L2CAP socket layer initialized
[ 0.339941] Bluetooth: SCO socket layer initialized
[ 0.345652] clocksource: Switched to clocksource riscv_clocksource
[ 0.359530] NET: Registered PF_INET protocol family
[ 0.365987] IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.381808] tcp_listen_portaddr_hash hash table entries: 4096 (order: 5, 163840 bytes, linear)
[ 0.391565] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.401034] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
[ 0.411754] TCP: Hash tables configured (established 65536 bind 65536)
[ 0.419267] UDP hash table entries: 4096 (order: 6, 393216 bytes, linear)
[ 0.427176] UDP-Lite hash table entries: 4096 (order: 6, 393216 bytes, linear)
[ 0.435773] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.442674] RPC: Registered named UNIX socket transport module.
[ 0.449223] RPC: Registered udp transport module.
[ 0.454399] RPC: Registered tcp transport module.
[ 0.459585] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.467408] PCI: CLS 0 bytes, default 64
[ 0.472403] Initialise system trusted keyrings
[ 0.476004] Unpacking initramfs…
[ 0.481198] workingset: timestamp_bits=62 max_order=21 bucket_order=0
[ 0.495960] NFS: Registering the id_resolver key type
[ 0.501564] Key type id_resolver registered
[ 0.506215] Key type id_legacy registered
[ 0.510738] nfs4filelayout_init: NFSv4 File Layout Driver Registering…
[ 0.518163] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering…
[ 0.526409] ntfs: driver 2.1.32 [Flags: R/W].
[ 0.531481] jffs2: version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
[ 0.538731] fuse: init (API version 7.34)
[ 0.582203] NET: Registered PF_ALG protocol family
[ 0.587533] Key type asymmetric registered
[ 0.592050] Asymmetric key parser ‘x509’ registered
[ 0.597550] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 0.605732] io scheduler mq-deadline registered
[ 0.610729] io scheduler kyber registered

tommythorn · January 18, 2023, 3:27am

I think you failed to read the thread. He has not been able to get any output.

Stromkiller · January 18, 2023, 10:33am

For what it is worth…
After updating the firmware using the SD card method and subsequently installing the '69 Debian variant, I have HDMI @ 2K/60 Hz on a cheap Benq monitor.
Response times are another matter…
Since I received the board, I have touched/adjusted NO hardware switches on the board.

Aubrey

Nurb432 · March 21, 2023, 9:06pm

Just wanted to add that that the starfive people reached out and took care of things for me. They are great people who care about their customers, even the one-offs.

rorden · May 19, 2023, 2:48pm

I have the same issue with my 8Gb LPDDR StarFive VisionFive2 starter kit. I have the DIP switches set to QSPI, I copied the disk image starfive-jh7110-VF2-VF2_515_v2.3.0-55.img as suggested by the quick start guide to the SD card using balena Etcher, insert the sd card, power-up. I get a green light but I never see a green light. I get the same outcome if the I have USB mouse/keyboard and HDMI monitor plugged in or no device plugged in.

Any other suggestions?

rorden · May 22, 2023, 2:29pm

As a followup, I found this web page that contradicts the quick start guide and says you should first boot with image-55 and then upgrade the BIOS. However, image-55 is no longer available. I did burn the more oldest image still available (image-69) and now when I boot I get both the constant red light and a blinking green light. On my modern monitor, a mouse cursor appears on a black screen but the cursor is frozen. Using a different keyboard, mouse and monitor (Dell 2009W 1680x1050) I get the solid red and blinking green light, but no cursor. Any suggestions.

rorden · May 22, 2023, 2:49pm

I also tried the sdcard.img and this gets a blinking green light, solid red light and text of booting to the screen. This seems to show percent completion, but gets stuck at 40.8906831 mipi_Op9: disabling .