This write-up is about integrating hardware intellectual property (IP) into a System on Chip (SoC).
One reason we did not choose a particular process node for a SoC we made in the past is that a peripheral team did not have resources for porting to that node. Although material savings far outweighed the NRE expense of porting, we had to forego on the material savings since we just did not have the people to do the port.
One reason we did not choose a particular process node for a SoC we made in the past is that a peripheral team did not have resources for porting to that node. Although material savings far outweighed the NRE expense of porting, we had to forego on the material savings since we just did not have the people to do the port.
How does one avoid this?
- Each team needs to incorporate external implementation into their delivery flow.
- Even in times of financial stability - when no resource constraints are on the horizon, one must be set up to switch to a 3rd party at moments notice.
- Keep IP delivery and minimum acceptable tests ready for delivery to a 3rd party. They are needed to qualify internal deliverables anyway.
- When IP is received, test it with the full set of tests and do final bug fixes in-house.
But will this will lead
to IP leakage?
- That's where "crown jewels" come in. Correctly classify the IP value ahead of time. Be selective in the classification.
Preparation
- Keep legal agreements and list of preferred vendors ready.
- Internal resources are needed to engage with 3rd party, qualify deliveries both ways and for final delivery to SoC team.
- Implement encryption options so that subsystems can only work with rest of the infrastructure.
Save money for the company. Deliver faster.
Kuntal.
No comments:
Post a Comment