Live data from Hacker News

Baochip-1x: What it is, why I'm doing it now and how it came about

crowdsupply.com

51–60 of 84 posts

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#51
post #36

Earlier quoted context omitted.

You do realize that violating export regulations is a much bigger risk than losing a few individuals relying on snake oil security?

Digikey and Mouser do not do this. > few individuals relying on snake oil security Please don't.

VPNs for desktop users have very few security use cases since most traffic ended up being https, but they're very useful for evading geoblocks.

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#52
post #47
post #12

Earlier quoted context omitted.

The masks alone are single digit millions, but with all the design tools and staff costs typically tens of millions is the benchmark number for a tape out in this node. After coming out of the fab, the chips go through probing, packaging and reeling.

> The masks alone are single digit millions, Ah, another reason why hardware erratas get fixed so rarely (I assume - along with retesting of course).

Most chips have basically one revision after first tapeout, because it's hard to get everything right first time. Small revisions can sometimes be done in the metal layer only, which is cheaper.

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#53
post #38

Earlier quoted context omitted.

You do realize that violating export regulations is a much bigger risk than losing a few individuals relying on snake oil security?

Can you explain what is the connection between closing the site to VPN users and violating export regulations?

I'd assume the point is that they think that the possibility of serving the website to an individual physically within a prohibited country constitutes unacceptable liability.

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#54
post #39

Wait a minute, why can't I reply to bunnie's top-level comment? Anyway, here's what I wanted to say: Adding your CPU to another company's silicon is a genius move, well done. I wonder why companies don't sell their spare die space to others, is it because of trust/risk?

> Wait a minute, why can't I reply to bunnie's top-level comment?

The powers that be here think they've found a bunch of "hacks" to curb off low quality comments.

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#56
post #45
post #39

Wait a minute, why can't I reply to bunnie's top-level comment? Anyway, here's what I wanted to say: Adding your CPU to another company's silicon is a genius move, well done. I wonder why companies don't sell their spare die space to others, is it because of trust/risk?

Crossbar is unusual to start with in that they wanted to do open RTL - so for starters, there's to a first order no companies even willing to discuss open RTL designs. Beyond that - mainly risk. I had to pinky swear that whatever I added would not break the chip, cause timing closure issues, delay the schedule, consume too much area or power, impact yield, I had to run my own validation and review program while meeti…

Having paid for multi-million dollar mask sets for ASICs before, I can confirm that this would take a lot of trust on Crossbar’s side. Great job on working with them.

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#57
post #51
post #36

Earlier quoted context omitted.

Digikey and Mouser do not do this. > few individuals relying on snake oil security Please don't.

VPNs for desktop users have very few security use cases since most traffic ended up being https, but they're very useful for evading geoblocks.

[deleted]

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#58
post #47
post #12

Earlier quoted context omitted.

The masks alone are single digit millions, but with all the design tools and staff costs typically tens of millions is the benchmark number for a tape out in this node. After coming out of the fab, the chips go through probing, packaging and reeling.

> The masks alone are single digit millions, Ah, another reason why hardware erratas get fixed so rarely (I assume - along with retesting of course).

Yes, exactly. A lot depends on your expected volume. Essentially, masks are your fixed tooling cost for chips. You then amortize that over your full volume. It’s easier to justify another mask set to fix bugs if you are going to be selling oodles of chips and the cost ends up being negligible and much harder to justify it if the volume is low. Years ago, I was CTO at a startup when our chips came back from fab. Everything looked good except for a silly error that our chief architect had made. He felt horrible for a couple weeks. He was a great architect (meticulous and precise) and I kept telling him that it was no use crying over spilled milk. Engineering is hard. But there went another few million dollars of precious venture capital up in smoke for the replacement mask sets.

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#59
MMU's have held sway for nearly 60 years, but I wonder if in ten years time when the AI is the whole stack/runs the whole stack and the majority of us wont be running anything but prompts they will be required. I have a big interest in how the AI will penetrate into the hardware level, not just as a sci-fi fan/author but as an electronics engineer/programmer. I should add that I doubt AI hardware will penetrate much into the embedded market due to cost.

Big fan of this project by the way.

Re: Baochip-1x: What it is, why I'm doing it now and how it came about

#60
post #45
post #39

Wait a minute, why can't I reply to bunnie's top-level comment? Anyway, here's what I wanted to say: Adding your CPU to another company's silicon is a genius move, well done. I wonder why companies don't sell their spare die space to others, is it because of trust/risk?

Crossbar is unusual to start with in that they wanted to do open RTL - so for starters, there's to a first order no companies even willing to discuss open RTL designs. Beyond that - mainly risk. I had to pinky swear that whatever I added would not break the chip, cause timing closure issues, delay the schedule, consume too much area or power, impact yield, I had to run my own validation and review program while meeti…

I'm basically ignorant of this entire space--I have mostly worked on SaaS products--so please forgive the question if it's too naive but as (the first?) someone who has just experienced this new and rare way of bringing a design to life are there any obvious process/tooling/whatever improvements you noticed that might make it less risky (and therefore less rare)? Reading your blog posts, the crowd supply materials, Xous docs, etc the burning thought at the front of my mind has been "there needs to be a lot more of this". Is there a path towards that?
Post reply on HN