LAUNCHXL-F28P65X: Serial Flash Programming Fails "Attempting autobaud to load kernel"

Hi Matt,

Thanks. That help me get a little further.  Now it looks like it is getting stuck loading the kernel file, shown here.

C2000 Serial Firmware Upgrader
Copyright (c) 2013 Texas Instruments Incorporated.  All rights reserved.

getting comm state
building comm DCB
adjusting port settings

calling f021_DownloadKernel CPU1 Kernel
Downloading c:\DevOps_SW\Workspace_Flash\flash_kernel_c28x_dual_ex1_c28x1.txt to device...

Attempting autobaud to load kernel...
Autobaud for kernel successful! Loading kernel file...
aa

I am using the command line args:  -d f28p65x -k c:\DevOps_SW\Workspace_Flash\flash_kernel_c28x_dual_ex1_c28x1.txt -a c:\DevOps_SW\Workspace_Flash\led_ex1_c28x_dual_blinky_cpu1.txt -b 9600 -p COM8 -v -w

I believe I am using the correct COM port # has shown here from the Windows Device Manager.

Do you have any suggestions?

Thanks,

Rob

Hi Rob, 

I can confirm your COM port and command line args look correct.

Have you tried the troubleshooting steps from the Serial Flash Programming Guide (Section 7.4)?

You've already configured boot option 3 (0x61), but there are additional steps for configuring the flash kernel. 

Best,

Matt

Hi Matt,

I rechecked everything in items 1-3 here in Serial Flash Programming Guide (Section 7.4) and I believe they are set correctly. 

After stepping through the serial_flash_programmer code, it is getting stuck on the "ReadFile(file, &rcvData, 1, &dwRead, NULL);" in function "loadProgram".
Function "ReadFile" is not returning.

Any thoughts?

Thanks,

Rob

Hi Rob,

So it seems the host is sending the first byte (AA) and is not receiving it back from the device. What state is the device boot ROM in? 

You can step through the device boot ROM by loading the boot ROM symbols (.out file) to the device. This option adds the symbols available in the generated project '.out' file for debugging purposes instead of loading the actual '.out' program onto the core via CCS - this is also why you can use this method with the boot ROM/built in bootloaders to debug and get visibility.

1. Open CCS to a workspace
2. Click 'view' > 'target configurations':
   1. 
3. You can import a project for this device to CCS and use that to connect to the device, or copy the raw target config from C2000Ware to the "user defined" target configurations in this window. Either way, find the device target config (example for F28377D below) and launch it:
   1. 
4. When it brings up the debug window, select the device CPU and connect to the target:
   1. 
5. Navigate to the toolbar and click the button to "load symbols"
   1. 
6. Load the boot ROM .out file. For F28P65x, it should be in 
   1. C2000Ware_Root\libraries\boot_rom\f28P65x\rev0\rom_sources\cpu1\ccs_files\Release
   2. If a window pops up saying it can't find the source file, you can select "Locate File" and find it in C2000Ware
      1. Usually here C2000Ware_Root\libraries\boot_rom\f28P65x\rev0\rom_sources\cpu1\F28P65x_ROM\bootROM\source
7. The file should open to show the location of the boot ROM you are at, and you can step through/debug

Best,

Matt

Hi Matt,

I do not see a 'view' > 'target configurations' menu item in the CCS, just a "Connected Targets" item.  Is it because I am using a new version of CCS?

Rob

Matt,

I found the "Load Symbols" option and tried it.

But it did not open the source file.  I was then able to get the debugger to break in what looks like the Boot ROM, but CCS is not finding the source files.  Even if I click on the "Browse.." button below and select the file it can't find, it still will not show it.

Rob

Hi Rob,

Apologies, those steps were made for an earlier version of CCS (v12).

Just to confirm, you're browsing to this path (and only selecting the folder, not any specific files)?

C2000Ware_5_04_00_00\libraries\boot_rom\f28P65x\rev0\rom_sources\cpu1\F28P65x_ROM\bootROM\source

Best,

Matt

Matt,

It only lets me select files, not folders.  So, I select C:\ti\c2000\C2000Ware_5_04_00_00\libraries\boot_rom\f28P65x\rev0\rom_sources\cpu1\F28P65x_ROM\bootROM\source\cpubrom_init_boot.asm.

But nothing happens.

Rob

Hi Rob,

That is unusual, I will check with the CCS team on how to load symbols on v20. If possible, I recommend using v12 for now to be able to debug in the boot ROM.

To confirm the steps I outlined above, I was able to successfully pass the autobaud lock and load an application to flash on my F28P65x LaunchPad, by only setting the predefined symbol in the kernel project (_LAUNCHXL_F28P65X) and changing the kernel's sciGetFunction() to take SCI_BOOT_ALT3 as an input (for boot option 0x61).

I just want to check a few things:

1. What hex utility arguments did you set for the kernel and application?
2. Is the kernel configured to build for RAM and the application to build for flash?
3. Can you try with a different USB cable?

Best,

Matt

Hi Matt,

Using CCS v20, I was NOT able to step through the BootROM and see the Loaded Symbols.  I have not tried on V12 and probably won't.  But it would be good to still know how to get this working for the future.

I retry following the steps again this morning and was able to get the Serial Flash Programming working.

I think my problem was doing a debug "Restart" and not doing a "CPU Reset" after modifying the RAM registers (0xD00, 0xD01, 0xD04).

After understanding the correct sequences of steps, I have been able to program the flash via the SCI several times at different baud rates.

Thanks for all your help,

Rob