-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Print chip features bitfield #10080
Conversation
Prints the value of the chip features bitfield to printChipInfo() to facilitate debugging.
👋 Hello Xylopyrographer, we appreciate your contribution to this project! Click to see more instructions ...
Review and merge process you can expect ...
|
Test Results 56 files - 83 56 suites - 83 4m 58s ⏱️ - 1h 37m 54s Results for commit 6db3430. ± Comparison against base commit f5be003. This pull request removes 9 tests.
♻️ This comment has been updated with latest results. |
thanks for the PR @Xylopyrographer, we will review it soon. |
Question is what does this help if the bits are examined in the following lines? This will just print a meaningless (to the users and us) hex, that we would need to examine anyway. Do you mean that there might be bits not documented? |
Memory usage test (comparing PR against master branch)The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.
Click to expand the detailed deltas report [usage change in BYTES]
|
@Xylopyrographer any comments? Thanks |
So this stems from #9974 where the chip report from a board using an ESP32-S3FH4R2 fails to report that the chip has both on-board flash and PSRAM. To help diagnose further, I had to add the raw chip features dump. Debugging and diagnostic tools should report accurately, this demonstrates a case where something is amiss. It would also be useful should new silicon be ahead of the chip report as it could be used as a check and yes, show undocumented features. As for interpretation, the bits are enumerated and can be checked (albeit with a bit more digging) but at least the base information is there to investigate further if needed. FWIW, haven't yet carried the investigation into the above error further. Not reported in IDF 4.4? Definition of "embedded" means something else? Does it show only for ESP32 modules? |
Description of Change
Adds printing the value of the chip features bitfield to printChipInfo() to facilitate debugging.
Tests scenarios
Tested with:
Related links
None