<!channel> - what would be the most helpful things...
# mpw-2-silicon
m
<!channel> - what would be the most helpful things Efabless can do to help you with your bringup? More office hours calls? A webinar? Please tell me your ideas in this thread
I'm also interested in how many people are actively working on this atm
and people totally blocked & why
i
I think a webinar will be ideal to have the more up-to-date information of how to do the bring up for then later develop some documentation. Regarding the active working, I'm working on it, but I'm block because external circumstances, I think next week I can continue on the bring up with better equipment.
t
I don’t have a MPW-2 project, but I take this as a more general question related to all project phases. My suggestion would be a pro-active documentation. In other words, picking up slack content (and other useful information) and converting it into a proper documentation. I’m not sure if the FAQ sheet was pro-actively executed. And I also don’t know if Efabless wants to pay money for someone driving this “pro-active documentation”. So a classical, more realistic proposal which might work could be a Wiki, which is driven by the community and people interested in can add to it. No need to elaborate on the advantages of a Wiki here. Cheers, Tobias PS1: Sorry if I just missed it and a Wiki already exists. PS2: Well, nowadays you might train a model with the slack content, but for now a Wiki might just do it.
a
more information about next run.
p
I think office hours would be helpful, where we show/review/try/discuss together.
s
I guess a webinar would be great for a broader audience at first and then for specific issues office hours can be utilized.
m
A wiki exists? where is it?
I've been blocked for a while and haven't done anything for a week: 1. On 1.2.0, I get "*** ERROR: failed to receive ready signal from firmware" repeatedly. Prior to 1.2.0, I would eventually get a Winbond SRAM not found, but now it seems to just keep flashing Caravel repeatedly ad infinitum. 2. I was getting no signal transitions and had added an error message to debug until the above error was added. 3. I can get it to flash the firmware (make F746ZG) if I change "--connect-under-reset" to "--reset" in the stflash command. 4. I measured the xclk and it seems a nice 10MHz. 5. I don't see any activity on SCK. I worry that my spring pins aren't making a solid connection. One of the suspicious ones is the CARAVEL_CSB signal.
y
For me it's very unclear what is expected to work and what isn't. It seems there's some disparate knowledge about this but nothing concrete. A page detailing the known issues, most probable cause and possible mitigations would be fantastic. To be honest I have been putting off trying to bring up my chips because I don't want to waste time if its not going to work. Clear info about is and isn't expected to work would help a lot
m
@yrrapt I've been pretty much waiting for people to "iron out the infrastructure" too.
k
@Matt Venn I’m a little late to this thread, but office hours would be really helpful! Are there office hours going on and if so, where can I find the schedule? I started bringing up my chip on Saturday and have been able to get up to the gpio_test passing thanks to the docs in caravel_board and help from Slack here. I am now trying to figure out everything that is needed to appropriately modify gpio_test for my use case (also posted the issues I’m facing in Slack on a separate thread).