- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How much code space is available for user programs in CCGx components.
I'd like a method to estimate the amount of functionality that can be incorporated into a selected CCG component along side the core USB-C Stack.
Which CCGx chips have enough code space to support reprogramming of other USB components such as re-driver chips.
This question is initially for CCG2. Other CCGx chips can be considered if they possess more program space next to the USB-C stack.
Is there a set size for the USB-C stack (the base firmware required to control USB-C interface negotiations) - or a way to determine the size for each CCGx component?
Greg
Solved! Go to Solution.
- Tags:
- ccg
- stack size
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Greg,
As per the table we attached on the websites.
All of below value is based on firmware build results, the value only for reference.
CCG2 firmware example code in SDK have used memory size as below:
Notebook: 29.5K
Power Adapter: 19.5KB
CCG3 firmware example code in latest SDK:
Notebook: 107.8KB
CCG3PA firmware example code in latest SDK:
Power BANK: 63.8KB
Power Adapter: 64KB
Best Regards,
Lisa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Greg,
As per the table we attached on the websites.
All of below value is based on firmware build results, the value only for reference.
CCG2 firmware example code in SDK have used memory size as below:
Notebook: 29.5K
Power Adapter: 19.5KB
CCG3 firmware example code in latest SDK:
Notebook: 107.8KB
CCG3PA firmware example code in latest SDK:
Power BANK: 63.8KB
Power Adapter: 64KB
Best Regards,
Lisa