Other Parts Discussed in Thread: C2000WARE
If USB storage is recognized by directly connecting USB Storage to the DSP Board without connecting to a computer with JTAG or other cables,
it tries to update the firmware.
Currently, I am looking at an example of F2837xD_usb_flash_kernels, but there is no response when the Out File of the example and
the Out File of Application are connected to USB.
The USB Flash Kernels example is supposed to be an example that reads USB data in conjunction with the USB Flash Programmer and
updates it to the DSP Flash Memory.
Is there a way to do the firmware update mentioned earlier by using the example alone?
Even if I don't dare use that example, I wonder if there is another way.
USB Flash Programmer's winusb or libusb was excluded from the test as it was seen to be necessary when connecting with Windows or Linux System.
If the F2837xD_usb_flash_kernels example is modified and used, it seems that the Kernel between the USB device and the DSP must be pierced,
so the *.dat file or *.out.
I think it is a preemptive task to transfer the out file to a USB device and connect it to the DSP Board.
At this time, how can the DSP Chip read the file in the USB storage?
If what I know is correct, I know that the DSP Chip's internal Boot Rom contains a code that can be booted according to the Boot Mode.
I would like to know if this code is correct for reading files into the device.
At this time, there is no need for drivers like winusb or libusb.
Looking at the code of usb_flash_programmer.exe, it was confirmed that files were searched for files with functions such as
fopen, fseek, and USB_SendData, and data was sent to USB.
If it is not connected to a PC, i.e., a DSP that is not a PC: Master-DSP: Slave structure will become a Master and read USB Data,
I am very curious if there is a need to replace that role of usb_flash_programmer.
Simply *.dat / *.out I strongly think that it will not be possible by putting out File in a USB device and connecting it to the DSP.
Assuming that functions such as fopen, fseek, and USB_SendData of usb_flash_programmer.exe code are added to the
F2837xD_usb_flash_kernels example and the output file path of the application code is specified, then the DSP uses *.dat / *.out.
How to recognize out File and how Kernel is created If you say that output file is recognized,
there is a question whether the output file of Application Code can also be recognized.