Other Parts Discussed in Thread: TMDSHSECDOCK
I'm following the document named "C2000 software Controlled Firmware Update Process".
I had a trouble while following "4.3 Firmware Update Process" step.
It seemed like signal doesn't transfer or receive anymore after tried one time.
Here is the situation I am investigating.
1. slow blinking LED example(led_ex1_blinky) is running in flash of MCU.
2. GPIO 15 (pin 63 in TMDSHSECDOCK) is connected with 1k resistor and 10nF capacitor in series and endpoint of capacitor is connected with GND pin in dock.
2. so D2 in ControlCARD's LED(GPIO 31) is bliinking now.
3. Open the CMD and type "serial_flash_programmer.exe -d f28004x -k flashapi_ex2_sci_kernel.txt -a led_ex1_blinky.txt -b 9600 -p COM10"
4. I can see the figure above.
I did this same thing with F28379d by following the document named "Serial Flash Programming of C2000 Microcontrollers"
I got the almost same trouble when I set the wrong bootmode(ex. using flash boot mode trying to download kernel using SCI).
After I set the proper boot mode, in F28379d, showed following properly working image.
So, I think the problem is related with something about bootmode setting.
In document, first step is making custom boot mode.
I checked whether the otp programming is well done or not.
The register refer in document is set properly as I can see the value through the CCS.
And also in hardware perspective, whatever I change the boot mode switch attached in ControlCARD(S1),
it only run by flash boot mode(I didn't connect any resistor and capacitor at "GPIO 15" at this moment).
So It means "GPIO 15" is properly set to custom boot mode and fixed by flash boot mode while LOW(0).
Then I connected 1k resistor and 10nF capactior to "GPIO 15", modified the kernel code explained in the
document section "4.2 Flash Kernel Modifications" and build by 7 CPU1_RAM mode, and get the
"flashapi_ex2_sci_kernel.txt" file from workspace folder, and tried to download the kernel. and It won't work as shown in top of this thread.
I checked example "sci_ex4_echoback" test to verify the sci-rx tx hadware parts were ok. and it worked fine.
So hardware part has no problem I think.
I tried to use new mcu device which is not configured custom boot mode as above, selected the switch as SCI boot mode at s1,
It shows proper downloading finish result as shown below
I think "request firmware update" of Figure 3, firmware update flow, and drive boot code from GPIO 15, this process is missing.
Is there any recommendation about this trouble?