Does ConfigBlock Editor support setting GPIO.BootConf in batch mode for VF50 V1.5.b4+?

Technical Support
, , , ,
1

I am trying to use the following within a file to set some GPIO on boot up along with some other configblock settings using the ConfigBlock Editor V1.6 in batch mode.

setconfig gpio.bootconf = “[gpio_5] altfn=-1 dir=out lvl=1 pull=none outmode=std [gpio_15] altfn=-1 dir=out lvl=1 pull=none outmode=std [gpio_111] altfn=-1 dir=out lvl=0 pull=none outmode=std [gpio_91] altfn=-1 dir=out lvl=1 pull=none outmode=std”
saveconfig gpio

[The setconfig and saveconfig each are a single line in the file]
Unfortunately, the GPIO settings do not seem to be taking hold.

Does command line mode in the ConfigBlock Editor change log mean something else other than batch mode? Is there an example of how to use the ConfigBlock Editor to set the GPIO.BootConf for configuring the boot GPIO settings?

Thank you.

2

I’m afraid this feature is not supported in the current version of the ConfigBlock Editor. We will add this feature in the next release of the tool.
Meanwhile you can use the Eboot command interface through the UART interface to configure the GPIO settings.

3

Has this feature been added in newer release of the ConfigBlock Editor (which is 1.9 in this moment)?

4

Yes this is supported. Currently there is an issue with the representation in the bootloader itself. The settings get truncated but they are applied to the hardware correctly. This will be solved in one of the next releases.