7.1./VTFT bug: CPU frequency reset when loading custom HW

[OT]

In 7.1.0/VTFT project settings, if a custom hardware setting is created, the CPU frequency and PLL setting in the main project settings are typically messed up, it does not obey the setting of the new VTFT hardware settings nor is it kept at the original values in the main project settings.

For instance I tried to create a custom setting for MMB dsPIC33 rev. 1.10_9A, but wanted the CPU frequency at 64 MHz, similar to ver. 1.05 board. So the CPU frequency was set to 64 MHz both in the main project setting and when creating a new VTFT hardware setting (including setting PLLFBD := 30). On the first attempt after loading the new setting PLL was turned off and CPU frequency set to 10MHz in the main settings. New attempt to create a hardware setting from the original one reset the CPU frequency back to 80 MHz, PLL setting of the primary oscillator mode was kept.

Apparently 7.1.0/VTFT tries to sync the main project settings automatically with that of the VTFT settings, but it does not work as intended if a custom hardware setting is used.

The custom hardware settings have also been troubled in the past: In VTFT 4.6.1, the settings under the "Set active" tab appears to be not saved at all, which makes the custom hardware settings saved by 4.6.1 unusable and will cause compile error on the missing procedures.

[OT]

Along with this, if a VTFT 4.6.1 project is imported that contains a custom HW setup, the oscillator settings in the main project configuration will loose the PLL setting.

[petar.suknjaja]

Hi,
We cannot declare it as a bug, but we can consider changing the way of loading custom schemes in project settings in future releases.
The solution would be creating the new config scheme, the one which you would pull through the board def.
Kind regards,
Petar

[OT]

The solution would be creating the new config scheme, the one which you would pull through the board def.

Thanks for the reply. I am not sure I understand what you mean by that last sentence?