beagleboard / beaglev-starlight Goto Github PK

@MichaelZhuxx commented:
starfive-tech/Fedora_on_StarFive#25 (comment)

we found the reason why our board could reset and beta board couldnt is that the schematic is updated. the beta board is remove the GPIO63 to trigger "CTRL1" on the pmic. Attached two version of schematic for your reference. @esmil thanks. we will fix it.

@esmil worked on TPS65086 restart in their Linux 5.12 branch and noticed that it would work better if the interrupt line from the TPS65086 was connected.

@esmil could you describe in more detail?

We will try to fix in the next PCB spin.

The extra LEDs are something we've become accustomed to having in the BeagleBone world. We can keep these compatible with our software for indicating disk activity, cpu activity and network connectivity.

This is a fundamental requirement for Linux kernel and u-boot developers.

I recommend using the UART connector on the BeagleBone AI or adding a USB-to-UART MCU. If you include the MCU, having the ability to power-down the board while the UART is connected is very useful.

Currently, the USB type-C is only capable of providing power. Further, the superspeed USB is only provided via 2 Type-A connectors. I think this is a huge limitation if the controller is dual-role capable.

It seems there is only one USB controller exposed and it goes to an on-board HUB, so that could dedicate it to being host-only all the time.

If nothing else, you could at least connect a USB to serial MCU via the Type-C connector to get to the debug console for a nice out-of-box for headless Linux users.

More thought needed here.

• What is the real functionality of the Pi header in terms of compatible functionality?
• Can we replace the header with a number of Grove and mikroBUS Click Shuttle headers (https://www.mikroe.com/shuttle-click)?

Probably too late for the 7100 version, but on-board eMMC makes things much more reliable for embedded into products and this is a must for the production 7110 version.

For Linux to handle board revisions, it is very handy to have a board ID.

For now, since we have SPI flash that is write-protected, I'd guess we could put the board ID into the SPI flash.

Anyway, I wanted to note this for discussion.

It seems that SPI is used for booting.

Are there any provisions for re-programming the SPI Flash? What happens if bad contents are programmed into the SPI Flash?

What boot modes are supported by the SoC ROM?

Is it possible to use a "BOOT button" similar to BeagleBone to enable UART/MMC/other boot based on the ROM bootloader?

In https://github.com/beagleboard/beaglev-starlight/blob/main/BeagleV_v0.9.pdf on sheet 12 of 17, there is a typo in the page name. It's titled "USB Tpye-C Power", which is a simple transposition error for "Type".

This is about the limit of my ability to recognize a bug in a schematic of this complexity. :-)

The JTAG signals don't seem to be connected. For some professional developers, this is a significant barrier. The TAGCONNECT footprint is rather small and folks needing JTAG shouldn't mind paying a bit more to get it connected.

@BBBSnowball commented:

The “Recover the bootloader” section shows a normal 3.3V USB-TTL adapter connected to the debug header. The signals on that header are labelled as 1V8. I think this ok anyway because there is a level shifter for RX (built with a pullup and a diode). However, be sure to get the connections right because there is a higher chance than usual to damage the SoC by connecting TX to TX. In addition, it is possible (but unlikely) that the TX levels are too low for some 3.3V adapters. We might want to collect some feedback on whether the usual ones (CH340, Prolific, FTDI) are ok.

The debug header is not populated on my board. If this is normal, you might want to mention that in the guide.

refer to forum post:
https://forum.beagleboard.org/t/update-bootloader-ddr-init-boot-u-boot-and-recover-bootloader/29558/7
(let me [Drew] know if you don't have access)

Please see this forum thread with @robertlipe and @BBBSnowball:
https://forum.beagleboard.org/t/jtag/28954/17

On page 5 of the BeagleV_Info.pdf the Ethernet PHY chip is maked as a LCD to HDMI converter IC.
The HDMI chip is the one next to the audio jack.

From @marckleinebudde in the forum:

the clearance on the raspi compatible mounting holes is not that great. Also having copper around the holes would be good, too.

@FionaYu20180326 would you be able to help @aswinvenu ?

He recreating the schematic in KiCad:
https://gitlab.com/aswinvenu/beaglev-kicad

He is trying to find information on:

1. UBF31-0171 - USB Type C connector from MTCONN
2. UAA111C-84161-4H - Dual Stacked USB3.0 Type A from FOXCONN
3. ST-HD-010 - HDMI connector from SHANQI
4. H9HCNNNCPUMLXR-NEE - 32Gb RAM from Hynix

This is also a post in the forum:
https://forum.beagleboard.org/t/beaglev-kicad/30006/6?u=drewfustini