Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Bootload_utils.dll is communication protocol agnostic, you have to provide the communication functions yourself in your application. By default, Bootload_utils.dll mostly just handles the bootloader logic, features such as security keys, and packet structure and then uses your custom written comm functions to actually send/receive commands to write/erase/read/etc.
It generally requires 4 functions:
int ReadData(int * buffer, int size)
int WriteData(int * buffer, int size)
In the case of a UART, OpenConnection would be written to open the COM port, CloseConnection would close the COM port, ReadData would receive the specified number of bytes to the specified buffer, and WriteData would write the specified number of bytes of the passed in buffer out. These functions would need to be written for the communication interface you wish to use.
As far as how to integrate it into Labview, I'm afraid I can't help much there (I haven't used LabView in probably around a decade, even then I barely used it). There's probably a way to do what you're looking to do. You would probably need to write the API functions to select a COM port and Baud Rate yourself, as well as the Open/Close/Read/Write functions, and then figure out how to link in bootloader_utils.dll to handle the bootload process itself.