This BeagleV looks like it would work well for me as it has Ethernet and USB ports.
1. With NetBSD, I can run out of memory with no major problems. With Linux, this has not been the case. I have to be more careful.
Could you elaborate a bit more on that, please ?
It's been a while since I last touched NetBSD, but I don't remember anything special regarding that aspect.
Then again, I've seen BSDs handle it even worse.
("tuning of" or "turning off")
Do you mean something like
sysctl vm.overcommit_memory=2Seems too late to edit now.
Note that one drawback with "disk-less" via read-only SD card or USB stick is how to have a good source of entropy at boot time.
Chromebooks are claimed to be 100% safe from certain types of attacks. The developers came up with this silly "whitewash" gimmick. Their motivation for a disk-less-like system is to force users to store personal data in the cloud. Ugh. Well, the disk-less systems I have been creating for recreational use long before Chromebooks existed are just as safe. Probably safer because I do not use a graphics layer or a web browser with Javascript interpeter.
Actually I saw recently some discussion exactly about that. I think many people would be glad to do it if they new how. It is not easy when you relatively new in the area. It is not too complicated but a lot of information and it is not obvious what is important and what not, so you read all and get overwhelmed easily.
>I do not run X11 anymore. I stay in VGA textmode. Doubt anyone would want to do exactly what I do.
I do exactly what you do, simply because x11 is not working on Pi with TV I have and I have nothing more since MBPro has simply died. (if you wish details, see here ”how“: https://news.ycombinator.com/item?id=25778247 )
>If you study how NetBSD's install media are created that will teach you almost everything you need to know. Happy to walk you through it though if you want to try NetBSD.
Thank you very much. This advice is already precious, because it helps to orient yourself in tons of info, and now I would know where to start digging. I would love to try once I’ll have equipment and time. I really wish to encourage you though to write down this process, I am sure there are some people who are desperately looking for this setup and how to achieve it properly, bothered with many questions. This guide could also be a good practical introduction into a NetBSD by the way.
>Chromebooks are claimed to be 100% safe from certain types of attacks. The developers came up with this silly "whitewash" gimmick. Their motivation for a disk-less-like system is to force users to store personal data in the cloud. Ugh.
it’s a shame really and done for wrong purpose. I never considered Chromebooks seriously for that reason.
>Well, the disk-less systems I have been creating for recreational use long before Chromebooks existed are just as safe. Probably safer because I do not use a graphics layer or a web browser with Javascript interpreter.
What I really like about it is the ability of fast recovery, which gives more freedom for experiments. I love it.
Not only does this type of setup give freedom for experiments (which NetBSD really does in general) but it makes expts easier. You can put multiple different kernels on the USB stick and reboot into each of them to test pros and cons of different release versions and/or configurations. Or you might boot one computer with kernel A, pull out the stick, insert into another computer and boot kernel B and run them simultaneously. No HDDs needed.
I might do a writeup; some users have done writeups on "disk-less" in the distant past. I have some simplification tricks no one has ever written about. However NetBSD has such great documentation relative to almost every other project and the developers tend to be "quietly competent" in the best way. It was never a culture of "HOW-TO's" as you will find in Linux. Studying the source and following source-changes and other mailing lists is better than any writeup, IMO.
It is like the old saw about teaching a man to fish. It is worth learning. Things do not change in NetBSD so fast or dramatically that what you have learnt will be later considered "obsolete".
PCIe, 16 GB DDR4, two M.2 (one for storage, one WIFI), quad core 1.5 GHz (same cores as this board, but twice as many)
I'm sure people would start comparing it pricewise to a i7 or something made at significant economies of scale. I think that is an unfair comparison due to the exotic CPU. Exotic in the sense that these aren't commodity CPUs.
I note that it has a PCIe x8 slot, but they don't have drivers for a video card (or any card) yet so it's kinda useless.
SiFive demonstrates the HiFive Unmatched using a $300 150W Radeon RX580. https://www.youtube.com/watch?v=HVsnnYuvDXI
You can complain that you don't want to spend that much on a graphics card [1] but you can't complain that it's not supported.
[1] cheaper ones will work too
You can sometimes hang a usb ethernet dongle off them but performance on those tend to be somewhat limited.
I used to wonder why embedded boards didn’t have multiple Ethernet boards and why it’s not common to use ethernet to connect to peripherals instead of “old interfaces”. Until I tried it for a project. It turns out Ethernet uses roughly 0.5 to 2W per port depending on speed (that’s 1-4W per connection).
The actual routing is done as a router-on-a-stick. It’s not perfect but it’s simple, scalable, and reliable.
Some of them have PCIE which you could connect a network card to. That seems like a more practical way to allow flexibility than having a lot of special purpose boards.
On lower end hardware you'd probably get higher throughput over the single link than trying to add a USB LAN adapter to it.
Could you say more about the use case you have in mind?
https://wiki.pine64.org/wiki/ROCKPro64
https://pine64.com/product/rockpro64-4gb-single-board-comput...
HardKernel/ODroid has things like the oDroid-HC4.
Also, USB3-to-SATA isn't completely crazy to do.
Lack of sata/m.2 port is very frustrating to me.
The Turing Pi project looks to do that with their next version: https://turingpi.com/v2/
Should be much more stable than a USB3 connection.
Sure, it would be great to have connectors for everything and support for every cool standard but these guys have to give up all what is non-essential to keep it small, cheap and possible to engineer by a small team.
There's no reason you couldn't kick SD transfer speeds up towards SSD speeds other than the protocol doesn't allow for it.
SD is fantastically simple, so that the boot rom can get at a bootloader without much effort (generally the bootrom just looks at a memory offset on the mmc device). Once you start speaking newer faster protocols, this simplicity is lost. You're not likely going to find a bootrom that implements all the bits needed to get u-boot from a sata device.
In a perfect world, once these are no longer developer devices, the mmc would be replaced with some spi flash (or even an emmc) with just u-boot.
On 90% of embedded dev systems, you're better off thinking of the sd card as a "bios chip" then a hard drive. The fact you can also use it as a block device to store a rw filesystem is almost incidental, and should probably be avoided.
Oh, that's a nice idea! It would be nice if you linked to a guide or wiki page so that more people can replicate your setup.
Also, CFast aren’t as ubiquitous as microSD. I can go to Target or Walmart and get a wide “selection” of microSD, but I’d be hard pressed to find a CFast card. So the chances of an SBC using CFast over eMMC or microSD is low.
There is one. It's called UFS 3.0. The Sony Xperia 1 II has it. They're same size as MicroSD, but look slightly different.
https://store.shopping.yahoo.co.jp/rarahu-store/B085B2LTLB.h...
https://www.samsung.com/semiconductor/minisite/ssd/download/...
I guess too little too late. None of the 4 dead Samsung cards I could find have the V mark (too old for that), required for validation, and they probably started adding support for regular EVO cards just a year ago or so.
Bought a cheap NUC with a disk and a BIOS and it is working like a champ - boots every time. I probably paid a little more but it's enough for my needs - a simple login and (occasional) DLNA server.
Also, when comparing costs you should take into account things like enclosure, power supply, as card(s) etc.
I'd say I probably paid around $250 or so for the NUC and a SODIMM and I had a SATA boot disk already. I had previously owned ODROID, libre computer (le potato), and Pi(s). These were probably in the ballpark of $80-$120 each, when including all the necessary equipment.
I'd far rather see a 2x PCIe port that could be used for whatever you wanted.
Raspberry pis are very popular as audio streamers, media centers that streams of the network, home automations etc.
But all or them greatly suffer from the fact that it can randomly die on you. Which is quite frustrating.
The only sensible solution (imho) to this currently is netbooting but it can be a hassle to setup in some cases.
An integrated 16GB emmc would do wonders for everything mentioned above.
And everybody bitches that the board is too expensive.
Beagle just doesn't offer anywhere near the same value.
The conversations always went like this:
"Cheaper? So, did you count the SD card you need for the RPi?"
"But it's cheaper."
"And the special power supply because the RPi power systems suck?"
"But it's cheaper."
"And the keyboard and monitor because it doesn't run headless over USB?"
"But it's cheaper."
"... Okay, boss, it's cheaper. Go have fun."
And that's before we even start talking about the lousy documentation of the RPi CPU chips. And the fact that the Ethernet was installed over the USB. etc.
But the RPi was cheaper. Shrug. The guys at TI learned their lesson. Throw everything off the board and make it cheap--the hackers don't give a shit about anything else.
The Pi is cheap, for a reason, but it is still more powerful than anything I use it for. But the same goes for the Beagle Board.
Choose the board you want, for the project you are doing.
Note: For every RPi project I have done, I have done two or three ESP8266/ESP32 projects along with five or six AVR/M0/M2 Arduino projects.
But if you vouch for it I'll take a closer look.
Now that's a valid argument. And I would argue it's way more than half.
If you want a one-off mumblesomething and can stay at the Linux OS level (ie. Web application, USB peripherals or maybe the most basic of GPIOs), the RPi ecosystem is going to let you get there much faster even though it will crash and burn occasionally. If that's "good enough" ... Douzou! ... Ganbatte! ... get moving and get going.
I have the same comment about Arduino. It ain't real reliable (but, to be fair, it's quite a bit more reliable than the RPis), but the ecosystem is awesome.
However, when you start asking something like "Gee, how do I send a single address byte over the I2C subsystem?" or "That signal needs a response in 50 nanoseconds, can I make that work?" you will thank the TI folks for producing that 5000 page (not joking or exaggerating) Technical Reference Manual.
One other thing that people who live in the RPi system always overlook in the Beagle ecosystem are the PRU cores. You can do HARD real-time work on those and still live in the Linux world. That's something that the RPi series just simply cannot do no matter how much you hack at them. And it often means the difference between a design which needs an FPGA and one that doesn't.
However, yes, you are going to live in that Technical Reference Manual for the Beagle series. If you're not comfortable doing that, then the Beagle stuff probably isn't for you.
There are really good reasons to use and love RPi's--ease of use is huge. But the whole "It's cheaper" thing just chaps my hide.
When you spend that much time with your device cost isn't a factor (imho). But the pi is cheap enough that I can gift one if I know the end result will work well. And it is quite nice to just have one lying around for when you get an itch.
Using netboot I have never had an issue with the pi. All reliability problems I've experienced can be tracked down bad power and SD-cards (note: I have not used any IO other than USB). Both are annoying enough to look for alternatives but both are also fixable (netbooting likely disqualifies it for many usecases though).
Minimizing reads on the sd card usually means that they work at least several years untouched (in my experience, obviously limited sample size), which is likely good enough for many (a true read-only system might work even better). But when the audio streamer in the vacation cabin dies when you aren't around to fix it is still frustrating. So I'm in the moment of figuring out how to move the last of them to be netbooted. Which has some very nice side-effects as well, such as trivial remote system backup+restores.
It also comes down to time. I know the pi and the pitfalls. Researching an alternative would take many hours and I'd still have to experience some of them. If the goal of the project isn't to learn a new sbc then that alone is a dealbreaker.
That said, PocketBeagle seems to support wifi netboot (which neither the pi and pi zero w do). Might be able to find a project for that!
PCIe, 16 GB DDR4, two M.2 (one for storage, one WIFI), quad core 1.5 GHz (same cores as this board, but twice as many)
I don't want to lug around anything, I want it to sit behind my monitor. Also an M.2 drive isn't that big, it could fit in many existing cases.
You want "industrial" cards from a vendor tailored to the space. I wouldn't trust even those new industrial sandisk cards.
1. Absolutely don't lie about their capacity
2. Have a reasonable MTBF
3. Are reliably fast
But instead we're all dealing with an industry that raced to the bottom years ago.
I'm concerned that the same mentality will infect the eMMC market eventually and it will become impossible to find quality parts after a couple of years.
It costs a pretty penny though. $40 for a 2GB non micro card was the last quote I got.
1. most SD card devices are battery powered
2. SD card failure is acceptable because they are replaceable
3. SD cards are not used as main storage for a computer
That leads to low quality SD cards.
I was also trying to run it as a NAS, so it had a decent amount of IO.
Maybe it could have been fixed with a better power supply, but switching over to the powered hub was easier to figure out.
faster-spinning-plates would draw more power, I guess.
The RaspberryPi is also "disk-less", which to me is one of the major limitations.
It's a super interesting little board, and I love that it's a RISC-V, that could really help getting the CPU in the hands of people. I just don't know enough about these things to understand why there are no storage connectors (other than an SD card slot).