Ok, followed Eric's suggestion on how to create a s19 file which turns out to be a *.hex file. When I drop the file onto the MSD drive
nothing happens. My application is trying to use the console function or printf out CDC to Tera Term. It works in the normal manner when using the debugger
agent and such, but thought this would be a cool path for customers who need a special demo and don't want to mess with code compilation. Is this beyond the scope of the MSD bootloader capabilities?
The file starts like this:
S0140000766973696F6E346C65676163792E68657837
S113000000300020FD060000F1080000FD0800009B
S1130010FD080000FD080000FD080000FD080000C8
.
.
.
解決済! 解決策の投稿を見る。
Can you try to use the DOS/cmd shell 'copy' command instead of using the Windows Explorer (press Windows+r, then enter the command 'cmd', then use the 'copy' command to copy the file to the bootloader).
I hope this helps.
Can you try to use the DOS/cmd shell 'copy' command instead of using the Windows Explorer (press Windows+r, then enter the command 'cmd', then use the 'copy' command to copy the file to the bootloader).
I hope this helps.