Live data from Hacker News

Milk-V Mars: RISC-V credit card size SBC

milkv.io

31–40 of 79 posts

Re: Milk-V Mars: RISC-V credit card size SBC

#31

How does it boot? Or is RISC-V going to follow the same problems as the ARM SBC system where each board has an obscure and unique boot process meaning images need to be carefully pre-built with who knows what installed for each board.

I'm not certain, but I think that's what opensbi is for: https://github.com/riscv-software-src/opensbi

Re: Milk-V Mars: RISC-V credit card size SBC

#33

there are so many SBCs these days. if you use them for hobby projects, many of them are fine. if you ever want to convert your project to something commercial, I would still consider raspberry pi and beaglebone instead based on software maturity and community support and their ecosystem at large. I really like NXP's i.MX6/8/9 chips, I wish there are some i.MX SBCs as popular as RPi and Beagles, for both hobby and com…

> I wish there are some i.MX SBC You can buy a Toradex, Variscite or PHYTEC module and pop a binary distro like Debian in there very easily. Disclosure: I work for one of the companies above.

I wish those SOM vendors can produce smaller and cheaper carrier boards with their popular SOM installed, basically becomes a SBC with SOM, so I can start with them before buying more SOMs down the road.

RPi did the right way in my opinion: its (cheap) SBC format gains attention widely, then it started to sell its own SOM in large volumes.

Re: Milk-V Mars: RISC-V credit card size SBC

#34

there are so many SBCs these days. if you use them for hobby projects, many of them are fine. if you ever want to convert your project to something commercial, I would still consider raspberry pi and beaglebone instead based on software maturity and community support and their ecosystem at large. I really like NXP's i.MX6/8/9 chips, I wish there are some i.MX SBCs as popular as RPi and Beagles, for both hobby and com…

I would tend to agree, but the supply limitations of the Pis has made me re-think that. I've heard with commercial agreements you can sometimes get Pis easier, but for launching a new product I'd be terrified that my growth would be hampered/limited by availability of the Pi

I have had zero problems getting pis for the past 3 years, but we generally pre-buy supply in bulk (500+)

Re: Milk-V Mars: RISC-V credit card size SBC

#37
post #34

Earlier quoted context omitted.

I would tend to agree, but the supply limitations of the Pis has made me re-think that. I've heard with commercial agreements you can sometimes get Pis easier, but for launching a new product I'd be terrified that my growth would be hampered/limited by availability of the Pi

I have had zero problems getting pis for the past 3 years, but we generally pre-buy supply in bulk (500+)

Out of curiosity, what is the channel for making a purchase like this? I am in that ballpark in terms of supply for CM4s.

Re: Milk-V Mars: RISC-V credit card size SBC

#38

Earlier quoted context omitted.

>if you ever want to convert your project to something commercial Surely at that point you would just treat the SBC as a reference design and fab your own boards?

A lot of commercial projects based on SBCs are relatively niche. It's very common to see things like lighting controllers, hobbyist stuff, etc, that's in the run size of 500 at the very most, basically be a raspberry pi with a custom hat in a custom plastic case. That can sustain a medium sized business. Designing and fabbing your own boards doesn't always make sense until you're on a version 2, or 3.

use CM4 modules with your own carrier board makes sense when you're building 500+.

I read somewhere if you're building more than 10,000 devices, it's better to design the whole PCB board on your own. Before that volume, using SOM modules for time to market could be more reasonable.

Re: Milk-V Mars: RISC-V credit card size SBC

#40

How does it boot? Or is RISC-V going to follow the same problems as the ARM SBC system where each board has an obscure and unique boot process meaning images need to be carefully pre-built with who knows what installed for each board.

I don't know about interrupts/device tree/etc. but at least for the boot process itself, UEFI/EDK2 was ported to RISC-V. (I actually learned this because I was looking up information about the Windows PE format and was surprised to see relocations support for RISC-V; they needed to add support for it to the PE specification since PE is the native binary format of UEFI!)
Post reply on HN