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
p

Praveen raj

04/01/2023, 7:38 PM
I'm confused with LA probes, please correct the understanding I have if it is wrong. Caravan template || firmware || Direction la_data_in -> reg_laX_data_in -> (project to CPU) la_data_out -> reg_laX_data -> (CPU to project) reg_laX_oenb -> Output enable -> Turn to 1 if CPU want to write to LA reg_laX_ienb -> Input enable -> Turn to 1 if CPU want to read to LA
t

Tim Edwards

04/02/2023, 2:06 AM
The "ienb" bits allow the CPU to accept input back from the user project (this includes enable bits for the wishbone signals passed back from the user project to the CPU). This is meant to protect the CPU from improper connections to the user project. The "oenb" bits do not control anything specific. They are expected to be used by the user project to inform the user project when a control signal is being applied on the corresponding la_data_out bit. The user project could then use that signal to multiplex an input between, say, the logic analyzer and an external pin. But you could in theory use the "oenb" bits as additional outputs.
👍 1
p

Praveen raj

04/02/2023, 1:12 PM
That make sense, Thanks!
@Tim Edwards Which means If I want to pass 1.8V from CPU to user project through the LA pin20-24, is the below description correct?
reg_la0_oenb = reg_la0_iena = 0x00000000;    // [31:0]
reg_la1_oenb = reg_la1_iena = 0x00000000;    // [63:32]
reg_la2_oenb = reg_la2_iena = 0x00000000;    // [95:64]
reg_la3_oenb = reg_la3_iena = 0x00000000;    // [127:96]
//Turning on LA 20:24
reg_la0_data = 0x01F00000; //[31:0]