Re: CAN Bootloader
It seems that there is bi-di communication when uploading a new firmware image? Im sure the EZBL comm tool takes care of this, but I assume you had to take this into account when you wrote your own program? I thought it would be unidirectional only: all that had to be done was send the bl2 file. But I am seeing a few FIFO write commands in the install 2 flash function. Also, was your CAN to USB adapter able to send data out a virtual COM port, or was it just a "normal" USB device? I was thinking if I got a CAN to USB adapter that enumerated as a virtual COM port, I could use the EZBL tool to send the firmware image, but right now I have the PEAK PCAN USB adapter. They do provide APIs for it, but this may be too complicated to get done in the short amount of time I have left. I might have to see if I can get that github version working.