jdkticom
jdkticom on Hacker News
correct, no NVIDIA hardware, just their NVDLA project which is open source.
http://nvdla.org.
Correct. This is open at the ISA, PCB and software level, not the chip RTL.
Still, it is a step forward.
For something more open at the RTL level, I'd look at Precuror (https://www.crowdsupply.com/sutajio-kosagi/precursor) right now.
Speaking as someone at Beagle, we see this board as an important step to more openness in the ecosystem, especially helping software developers improve the state of open source for RISC-V. It is also just a really cool board. Beagle will do more to try to get more openness at the RTL-level moving forward, perhaps even with FPGA boards at an interim step. The shuttle services are starting to make releasing a new chip design in reasonably modern nodes more possible.
One of the other replies points to the RISC-V extensions feature. I think for someone who "doesn't care about openness" would at least benefit from that in the architecture. It means the same compiler can be used to bootstrap things and simple steps can be added to greatly optimize specific types of code, like AI stuff. This board really stands out in AI performance.
Also, having things open means that the supply-chain can be more stable, with less chances of a single glitch in the system halting deliveries for any time. This is driving a lot of interest in RISC-V right now.
0.5ms event-to-output, 1ms input-to-process-to-output.
pureData, supercollider, and C++ programming API.
Built-in web-IDE and tutorials.
Faster, newer generation CPU (Zero moved back to ARMv6). Additional microcontrollers (2x PRU, 1x M3). ADC. More I/O capability. Open hardware with a (yet to be proven, but I'm very confident) much higher availability for use in projects, etc.---and also simple to clone/extend if you want to make your own. Also, better processor documentation.
I made priority of choosing pins not used by LCD or eMMC on BeagleBone Black so that many capes not reassigning those pins could be adapted. The pinout was also done to work with a large number of existing breakout boards.
The EEPROM identifier requires a small update to the bootloader and device tree.
Many are, but some have reasonable sized keyboards. I prefer some of the older models.
Yes, that's how I typically do workshops is with Chromebooks.
I'll be showing off an infrared camera and a handheld MAME console I built at Maker Faire New York then sharing the design info. Working on pushing to github later this afternoon.
Using VNC is a legitimate way to develop for this, but mostly it is done through web browsers (Cloud9 IDE) and direct ssh.
It is definitely not sold at a loss. No maximum to the order quantity, just lead time if it is more than inventory.
And USB on the headers, making it easy to build a board with a hub or whatever, including USB WiFi modules.
It does not have HDMI. Displays would typically be done with SPI breakout boards like from Sparkfun and Adafruit. You could also do a display via USB to VGA/HDMI.