Using BCDEdit kernel debugging can be set on or off on Command Line Interface(admin mode) with:
bcdedit /debug [{ID}] { on | off }
{ID} is optional boot loader id and if not present addresses {current} - the boot loader used for booting the running OS.
Using Visual BCD Editor you can enable/disable kernel debugging for a loader by creating the element "KernelDebuggerEnabled" (if not already present) and setting its value to true/false.
To specify debugger connection options you can use the elements of {dbgsettings}.
Using bcdedit you can specify following dbgsettings:
Standard is debugger connection on serial port 1 and baud rate 115200.
All equvalent Visual BCD debug settings elements are Library type elements:
SerialDebuggerPort
SerialDebuggerPortAddress
SerialDebuggerBaudRate
1394DebuggerChannel
UsbDebuggerTargetName
DebuggerStartPolicy
DebuggerIgnoreUsermodeExceptions
Command for USB debug settings and Visual BCD equivalent:
bcdedit /dbgsettings USB TARGETNAME:MyTargetName /start autoenable /noumex
If you want to load/debug a 64-bit driver you can use boolean element "AllowPrereleaseSignatures" which is the eqivalent for
bcd /set testsigning on|off
which enables/disables loading and debugging of 64-bit drivers for the OS loaded by {current}.
The driver has to be signed but you can use any certificate during testing.
See Microsoft document Getting Started with Windows Debugging.
It takes some time and effort to code apps and maintain a website, and liters of coffee ;)