(https://www.media.volvocars.com/global/en-gb/media/pressrele...)
344 karma · joined March 17, 2010
https://twitter.com/krigle
(https://www.media.volvocars.com/global/en-gb/media/pressrele...)
Have a look at BitHub: https://github.com/WhisperSystems/BitHub
But for advanced ADAS/AD and IVI it is ARM or Intel.
It is an easy solutions which ensures integrity and has few drawbacks for typical embedded systems.
The output of a typical Embedded Linux CI build is a complete RFS, having to care about individual packages would just be a headache, when you can replace the entire RFS and be done with it.
Cameras + radar is more than humans have at least, so I think that should be enough.
Solid state LIDARs will soon be cheap enough and a good complement of course but I find it hard to believe autonomous driving would be impossible without it.
It would probably force the hw manufacturer to think through its design a little bit more, which would be a good thing. I've seen enough of these SoCs with "complex system of interacting components" to feel that a well thought out design that needs less static description of SoC/board/cpu level details would be beneficial.
Device trees are needed because manufacturers did not create self describing hardware.
One good reason for using Linux instead of any of the RTOS is better networking support. I've used VxWorks, RTEMS, Nucleus, FreeRTOS, eCos, etc and their networking stacks are all pretty slow and crappy.
I do embedded software of all kinds. Bare metal, RTOS, Linux (including kernel/driver work).
Experience from semiconductor (SoC vendor), aerospace, telecom and imaging.
se.linkedin.com/in/kristofferglembo
kristofferglembo at gmail dot com
Sure you have Thumb, that saves a little on memory bandwidth which is good. But nobody uses it anyways, and you might run slower so you can't sleep as fast.
I like the J2 (the open source sh) project as well but it doesn't have a MMU which rules it out for anything but simpler embedded projects.
Wrapping up one or multiple of the RISC-V cores in GRLIB is something I think would benefit both Gaisler and the RISC-V community and something I have thought of doing myself if I had the time!
But the SPARCs you mention have their drawbacks. LEON is not that competetive in the high end (in order single issue, low clock freq) and T1/T2 are only cores (i.e. without interesting "uncore" stuff) and not that good as general purpose "desktop like" CPU.
I have much higher hopes for RISC-V, the community is really booming and the architecture is better than SPARC.
I say this as a former Gaisler employee and SPARC proponent :-)
Regarding FPGA, of course you don't do the complete implementation in it, you accelerate the low level stuff, FFTs, coding, etc, as are already done in all baseband dsps.
And LTE CC is not the necessarily a good way to get multi-Gbps due to radio complexity.