Community
Participate
Working Groups
Steps to reproduce problem -------------------------- 1. Create a RTSC configuration project for the MSP430 family and the MSP430F5438 device. Add the attached 'cfg' file to the project 2. Start XGCONF by doubleclicking on the file in the project 3. Add the BIOS6 'Task' module to the configuration. 4. The 'numPriorities' config parameter is set to 1 in the "Properties" tab. There is also a error in the hover text which says the default priority is 16 while a value of 1 is shown. Change the 'numPriorities' to 55. XGCONF will re-validate. During re-validation the 'numPriorities' is shown as "null". The validation completes but XGCONF does not report an error for incorrect priorities in the problems view. The 'numPriorities' value is set to 1 as before. 5. Delete all lines from the script except the last two lines referring to the 'Task' module. Re-validate. This time the error shows up in the problems view.
Changed to P1, likely indicates other problems.
Created attachment 169876 [details] RTSC configuration file
Created attachment 169877 [details] RTSC configuration file
This is not an XGCONF error. The attached .cfg file sets BIOS.taskEnabled to false, which disables the Task module. Task module sets its own numPriorites to 1 in this case to minimize footprint, overriding any user setting, and reports no error. Changing BIOS.taskEnabled to true allows the user to change numPriorities. In this case Task module reports an error if the user sets numPriorities to 55, which XGCONF displays correctly. The hover text initially shown indicating a default numPriorities of 16 is hard-coded in Task module XDOC summary, which XGCONF displays correctly. A minimal fix that BIOS could implement would be for Task module to issue a warning when Task is used but taskEnabled is false. The warning could be flagged against the Task module, or maybe better BIOS.taskEnabled, and XGCONF would display this icon. The numPriorities field displaying as null is generic XGCONF behavior during validation, when the execution results are inaccessible. This could be improved. Please file a separate bug for this if desired, as the description and priority of the current bug would not be appropriate.
Invalid bug
