henk
Thanks! When I comment a task away from the placed par, like this:
Code: Select all
// on tile[0].core[0]: temperature_heat_controller (i_temperature_heat_commands, i_i2c_external_commands[1], i_port_heat_light_commands[1]);
I get the following warning report:
Code: Select all
`i_temperature_heat_commands' not used in two parallel statements ...
`i_port_heat_light_commands' not used in two parallel statements (byte range 4..8) ...
`i_i2c_external_commands' not used in two parallel statements (byte range 4..8) ...
The last two interfaces arrays are size 2 and it's [1] that's not used for both.
If I switch the ends of the first interface array (the middle parameter: i_i2c_external_commands) and comment it away:
Code: Select all
// on tile[0].core[0]: temperature_heat_controller (i_temperature_heat_commands, i_i2c_external_commands[0], i_port_heat_light_commands[1]);
I get the following warning report:
Code: Select all
`i_temperature_heat_commands' not used in two parallel statements ...
`i_port_heat_light_commands' not used in two parallel statements (byte range 4..8) ...
`i_i2c_external_commands' not used in two parallel statements (byte range 0..4) ...
The last two interfaces arrays are size 2 and it's [0] that's not used in the first and [1] that's not used in the second.
Array size: 2
Not used [0]: byte range 0..4 (formula?: range first value 0 divided by size 2 = index 0 not used)
Not used [1]: byte range 4..8 (formula?: range first value 4 divided by size 2 = index 1 not used)
Is this correct? Is this internal info only nice to know for me?
Still don't
really understand the figures 0..4 and 4..8 and the the term "byte range"...