From: David Picard <david.picard@clermont.in2p3.fr>
To: MList-Barebox <barebox@lists.infradead.org>
Subject: moving to same chip, different board: no console output
Date: Fri, 6 Jun 2025 16:43:58 +0200 [thread overview]
Message-ID: <f8c5021d-3dcb-47b5-8f27-09e33991d6ea@clermont.in2p3.fr> (raw)
Hello,
I am working on a project for which we selected an Intel/Altera Cyclone
5 SoC FPGA (an FPGA with an ARM core). As the project evolves, I have to
change boards and I am facing issues to boot: absolutely no output on
the serial console (USB virtual COM port), not even from Barebox.
Previous working configuration:
- SD card image produced by Buildroot with Barebox as the bootloader
- Terasic ADC-SoC demo board, booting from the SD card.
https://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=English&No=1061&PartNo=1
Current non-working configuration:
- Eclustra Mercury+ SA2 module, also with a Cyclone 5, plus SDRAM, RTC,
QSPI flash, etc. I think that the main difference between both Cyclone 5
chips is the size of the logic section is bigger on the module. The
module has more RAM.
https://www.enclustra.com/en/products/system-on-chip-modules/mercury-sa2/
- Enclustra ST1 demo baseboard. It has a JTAG port, should this
information be of interest.
https://www.enclustra.com/en/products/base-boards/mercury-st1/
I the current configuration, I get no output on the serial console.
What I did:
- I checked the hardware configuration (switches to select booting from
the SD card and USB config) with a bare-metal application provided by
Enclustra.
- I used Enclutra's .dts and .dtsi files, which differ very slightly
from the Linux kernel tree files.
- I checked how the SD card is connected: to the exact same pins in both
configurations.
- I had a look at Barebox menuconfig, but nothing caught my eye.
So, now I'm stuck, and I'm looking for some guidance.
David
next reply other threads:[~2025-06-06 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 14:43 David Picard [this message]
2025-06-06 17:46 ` Ahmad Fatoum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8c5021d-3dcb-47b5-8f27-09e33991d6ea@clermont.in2p3.fr \
--to=david.picard@clermont.in2p3.fr \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox