Using adnl burn mode with Khadas VIM4 and other modern amlogic SoCs? - Android Stick & Console AMLogic based Computers

Modern amlogic SoCs seem to have done away with v2 usbburning mode (aml v2 factory burn) using the worldcup drivers with the command line "update" utility and the GUI usb burning tool. The reference u-boot code for these new SoCs does not seem to have the possibility to use the legacy v2 usbburning mode code.
This is apparent in the soon-to-be-released Khadas VIM4, as well as all presently released amlogic designs using the S905X4, including askey's sti6220d315, sei's SEI800 series, and videostrong's ka2, amongst others. It is also the case for all recently released devices using the S905Y4 SoC, like sdmc's dv6071z and sei's SEI700 series.
The replacement for v2 usbburning mode in these devices is adnl (amlogic DNL protocol);
Code:
adnl - use Amlogic DNL protocol
Amlogic DNL protocol appears to use ordinary fastboot/adb style drivers. But the ordinary fastboot host-side tool is not sufficient in order to fully utilize amlogic DNL protocol. Khadas has posted a linux adnl host-side tool binary on github.
Khadas also has posted a win32 adnl host-side tool binary package, aml_dnl-win32.zip. The help screen and some usage examples are shown below:
Code:
adnl.exe -h
Amlogic DNL protocol tool V[2.6.3] at Aug 20 2021
usage: adnl [ -s <specific para> ] <command> <command para>
commands:
devices List all connected dnl devices
getvar <variable> Display a BL1/BL2/BL33 variable.
if not supported, this does nothing.
setvar <variable> <value> Set a BL1 <variable> with <value>.
setkey <keyPath> Set a BL1 <variable> with <value>.
oem/cmd <cmd> Send a BL33 string<cmd>.
download <FilePath> [<size> <offset>]
Download file to RAM[, with <size>bytes from <offset>]
run boot code in RAM, after cmd 'download'.
bl1_boot -f <bootloaderPath> BL1 download and boot bl2.
bl2_boot -f <bootloaderPath> BL2 download and boot TPL.
partition <-p partName> <-f imgPath> [<-m media>] [<-t imgType>] [-v vryFile]
@media: mem/store/key, default store
@imgType: sparse/normal, default normal
upload <-p partName> <-f dumpFilePath> <-z dumpSz [K|M|G]> [<-m media>] [<-o offset>]
@media: mem/store/key, default store
@offset: start offset in part @partname, default 0
reboot [mode] Reboot device [into supported mode].
other options:
-s <specific para> specify a USB device, command 'devices' to get specific para
-h, --help show this message.
Beyond the help screen, documentation for (or examples using) the amlogic DNL protocol host-side tool is pretty sparse. Although It seems that most of the functionality that is in the old worldcup host-side tool is also present in the adnl host-side tool.
I've found only this single post that referenced using the windows binary, which included these images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}