Two issues:

1/ In the pathfinder_system example (AADLib), in the xml file, a task (for example prs_PSC.data_distribution from aadl model) becomes prs_psc_data_distribution while the shared data (data_rw) is accessed by the (same) task <resource_user>data_distribution 1 1</resource_user>. Consequently, the same task in the AADL model has two different names in the cheddar configuration file.

2/ Plus, the resource is occupied by the task for 1 ms, while the case study said that any task gets the needed resource during it full execution time. Maybe it is possible to precise this last point through the aadl model (but it is not the case in the example).