https://open-source-silicon.dev logo
Channels
aa
abcc
activity
adiabatonauts
analog-design
announce
announcements
b2aws
b2aws-tutorial
bag
basebands
beagleboard
bluetooth
board-respin
cadence-genus
cadence-innovus
cadence-spectre
cadence-virtuoso
caravan
caravel
caravel-board
chilechipmakers
chip-yard
chipignite
chipignite2206q_stanford_bringup
chisel
coalition-for-digital-environmental-sustainability
community_denmark_dtu
containers
courses
design-review
design-services
dffram
digital-design
digital-electronics-learners
discord-mods
dynamic-power-estimation
efabless
electric
events
fasoc
fault
foss-asic-tools
fossee-iitb-esim
fossee-iitb-google-sky130
fpga
funding
fuserisc
general
generative-ai-silicon-challenge
genius-vlsi
gf180
gf180mcu
hardware-beginners
help-
ieee-sscs-cac-23
ieee-sscs-dc-21q3
ieee-sscs-dc-22
ieee-sscs-dc-23
ihp-sg13g2
images
infiniband
j-core
japan-region
junk
klayout
latam_vlsi
layouteditor
lvs
lvs-analysis
magic
magical
maker-projects
maker-zone
microwatt
mpw-2-silicon
mpw-one-clean-short
mpw-one-silicon
neuro-mem
nydesign
open_pdks
open-pdk
openadiabaticlogic
openfpga
openhighqualityresonators
openlane
openlane_cloudrunner
openlane-development
openocd
openpositarithmetic
openpower
openram
openroad
opentitan
osu
pa-test-chip
paracells
pd-openlane-and-sky130
picosoc
pll
popy_neel
power
private-shuttle
rad-lab-silicon
radio
rdircd
reram
researchers
rf-mmw-design
rios
riscv
sdram
serdes
shuttle
shuttle-precheck
shuttle-status
silicon-photonics
silicon-validation
silicon-validation-private
sky130
sky130-ci
sky130-pv-workshop
sky65
sky90
skywater
sram
stdcelllib
strive
swerv
system-verilog-learners
tapeout-job
tapeout-pakistan
team-awesome
timing-closure
toysram
travis-ci
uvm-learners
vendor-synopsys
venn
verification-be
verification-fe
verilog-learners
vh2v
vhdl
vhdl-learners
vliw
vlsi_verilog_using_opensource_eda
vlsi_verilog_using_opensoure_eda
vlsi-learners-group
vlsi101
waveform-viewers
xls
xschem
xyce
zettascale
Powered by
Title
j

jeffdi

02/07/2023, 6:57 AM
***************** <!channel> Hello, We’ve identified an issue effect silicon testing for MPW-2 projects using Caravan (
user_analog_project_wrapper
). We found that there are two connections missing from the management area to IO[0] and IO[1]. This was affecting the Nucleo diagnostic test for these projects. The primary symptom is a user would get a “Winbond SRAM” error when trying to run the diagnostic. It also means these IO pads can not be used as outputs for the management SoC. The Nucleo software has been updated to work around this issue. The new version (1.2.0) has been pushed to the caravel_board repo. The README has been updated to explain how to run the diagnostic for analog projects (see ’make run_analog PART=<id>). Below is a link to the updated README… https://github.com/efabless/caravel_board/blob/main/firmware_vex/nucleo/README.pdf ******************
👀 2
m

Mitch Bailey

02/28/2023, 3:20 AM
@jeffdi @Tim Edwards These 4 signals, right?
/gpio_control_bidir_1\[0\]/mgmt_gpio_oeb
/gpio_control_bidir_1\[0\]/mgmt_gpio_out
/gpio_control_bidir_1\[1\]/mgmt_gpio_oeb
/gpio_control_bidir_1\[1\]/mgmt_gpio_out
t

Tim Edwards

02/28/2023, 3:35 AM
Yes, those are the ones. They should be pretty clear in a top level LVS.
m

Mitch Bailey

02/28/2023, 4:11 AM
I think they were disconnected in the verilog also, so LVS matches. I got those from the CVC results.
caravan.v
has had
jtag_out
,
jtag_outenb
and
sdo_out
,
sdo_outenb
that only connect to `gpio_control_block`s.
caravel.v
has
mgmt_io_out[0:1]
and
mgmt_io_oeb[0:1]
from
housekeeping
connected to the corresponding blocks. (edit: note this is on MPW-2. The current
caravan.v
does not use
jtag_out*
or
sdo_out*
.)
t

Tim Edwards

02/28/2023, 2:58 PM
Okay. I guess it simplifies things if it just passes LVS. The error is known to have been fixed, so I'm not worrying about it too much other than noting how it affects Caravan projects for MPW-two. It's actually a relief to know that the MPW-two Caravan projects actually work; by not being able to talk to the housekeeping SPI, I had passed them off as untestable for a long time, until Jeff proved that they were able to run a program if it was already in the SPI flash, and I found out that the Nucleo hat was set up in a way that let the Nucleo read the data coming back from the SPI flash directly, bypassing GPIO 1 (SDO).