Skip to content

Removed documentation about read-only part of TOC cache. #768

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.

Sign up for GitHub

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

Merged
stefanthorstenson merged 1 commit into from
Jan 19, 2026
Merged

Removed documentation about read-only part of TOC cache. #768

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/development/dev_info_client.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,9 +197,7 @@ are cached ([more info on logging/parameter frameworks and
TOC](https://www.bitcraze.io/documentation/repository/crazyflie-firmware/master/) ). The writable part of the TOC
cache is located in *<local_config_folder>/cache* where each cache is saved in a file
named after the CRC32 (in hex) of the TOC CRC32 (for example
*1CB41680.json*). There\'s also a read-only part of the TOC cache
that\'s located in */lib/cglib/cache* (NOTE: not sure about this one!) and contains the caches for
official builds. When the application connects to a Crazyflie the CRC32
*1CB41680.json*). When the application connects to a Crazyflie the CRC32
of the log and param TOC is requested. When the client receives it will
check if a file with the correct name exists (in both the RW and the RO
TOC cache). If it does it will load the cached TOC, if not it will start
Expand Down