Do you really need source code?
Colin Walls, Mentor Embedded
embedded.com (August 09, 2014)
If you ask any embedded software developer whether they would like access to the source code for the real time operating system that they have selected, the answer would almost certainly be yes. Likewise for any other software IP. This article investigates whether this is a sensible answer in all cases and looks at when and why source code is needed and why sometimes it may be less useful than anticipated.
Why source code?
There are a number of key criteria that engineers apply when selecting a real time operating system (RTOS). Many of them – cost, functionality, licensing, support – make a lot of sense. However, another one – availability of source code – may be less logical, but is always rated as a strong factor.
Source code being available does not mean that it is supplied automatically and free of charge. This may be the case with some commercial products, and, of course, open source products intrinsically include source code. However, other vendors may choose to charge for source code or not make it available at all.
The reasons for wanting source code need to be examined in some detail so its suitability as a selection criterion may be assessed.
To read the full article, click here
Related Semiconductor IP
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
Related Articles
- IP vendors making leap from source code to silicon
- "You didn't want to do that..."
- Why you need RTL virtual prototyping
- Commentary: Synopsys memory IP users seek RTL source code
Latest Articles
- A Secure dToF LiDAR SoC with Dual-Domain Fingerprinting and Event-Driven AFE Circuit Achieving Sensor-Level Attack Resilience
- ZTA-Q: an Open-source RISC-V Platform for Accurate Quantized CNN Inference
- Automated Pre-Silicon Verification of High-Speed DDR5 and LPDDR5/6 Memory Controllers: Closed-Loop Timing, Mode Register, and PHY Synchronization in UVM
- U-Sonic: An Open-Source 8-Channel Ultrasound Transmit IP in a 130 nm RISC-V SoC
- S-ALSA: Co-Design of Adiabatic Logic-based Sensing and Balanced Bit-Cells for Secure and Energy-Efficient MRAM