hi all,
I am using TMS570Ls3137 HDK board,halcogen 4, ucos-iii.I want to dump my code through bootloader.So pls help me how to add uart bootloader code in my application.
Apparently you are missing the Flash API library.
If installed, it is by default in C:\ti\Hercules\F021 Flash API\02.01.00
It is usually installed with Halcogen package. Tha actual release you can download is 02.01.01 but is not compatible with the Bootloader.
As I mentioned, Flash API 02.01.00 has to be used with bootloader. We are working on a new version of bootloader to work with 02.01.01
The download page for Flash API is: 
I will send you as zip file the version 02.01.00
Can you also check on your PC if it is installed and let me know the version(s) you have.
Pandurang,
Can you tell me the path installation for the Flash_API.
In the project I've sent to you, the expected path for this Flash_API library is C:\ti\Hercules\F021 Flash API\02.01.00
If for some reason your installation is different, than the library will not be found at link time.
Here is how to change the project in case Flash_API in your case is not installed at the default location.
1] Right click on your project name in the project explorer window and select "Show Build Settings".
2] Expand CCS Build->ARM Linker->File Search Path as shown below.
If the path is incorrect, double click and edit with the correct path.
Please have a try and let me know.
Pandurang,
This is good news.
What you have to do is to program on your device the UART bootloader first.
This will erase the device and program the bootloader.
Start your Hyperterminal (you have to have the usb cable plugged between your HDK and your PC.
Here is the configuration for Hyperterminal. In my setup I use Tera Term VT.
The COM port will certainly be different in your case. The default baudrate has to be set as 115200 as shown in the above picture.
The next step is to run the bootloader. It will check if there is a valid application code.
Right now there is no application so it will be in download mode.
You should see this on your terminal:
Before going further, the bootloader is using YMODEM protocol to download binary code to the device:
In Tera Term you have to go through File->Transfer->YMODEM->Send and select the file you want to download.
In my example, it is TMS570LS3137_Blinky_Bootloader.bin from the release directory.
As I said in a previous post, the release version is linked at address 0x0002_0000
So to start the download, from the Hyperterminal click option 1 "Download Application Image To the Internal Flash"
In Tera Term you have to go through File->Transfer->YMODEM->Send and select the file you want to download.
With my demo code you have to select: TMS570LS3137_Blinky_Bootloader.bin
In your case, you will have to select your application code.
You should see a progress bar going on. This will confirm that download is in progress.
Now, if you click option 3 in the Hyperterminal, the bootloader will execute your application code.
With my demo code, you should see an LED blinking on the HDK.
So there is nothing to merge. The bootloader is one project, your application is a different project.
Use my demo code to understand the concept before trying to download your application.
Good luck.
Pandurang,
I was able to use your code and program it via bootloader.
Here are what I had to change.
1] Not sure if this is an artifact of importing your project in my environment, but the Post-Build step to generate the bin file was missing.
Here is the full command line:
"${CCE_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin.bat" "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" "${CG_TOOL_ROOT}/bin/armofd.exe" "${CG_TOOL_ROOT}/bin/armhex.exe" "${CCE_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin.exe"
2] This is the most important part, and in my previous reply I've mentioned it many times.
The bootloader EXPECT your application code to be mapped at address 0x0020_0000 AND NOT 0x0000_0000
In your case, it was 0x0000_0000.
To be able to debug the application to be downloaded I create via CCS a debug and release version. The debug version uses a linker command file where the flash is mapped to 0x0000_0000. In this case the code can be programmed via CCS directly and there is no need to use the bootloader.
Once the code is debugged, than I create the release version. This version uses a different linker command file where the flash is now mapped to 0x0020_0000.
I've attached to this post the 2 linker command file for your reference. These linker command files can be copied in:
\Micrium_TMS570LS31xHDK_OS3\Micrium\Examples\TI\TMS570LS31xHDK\BSP\CCS-HCG\source directory.
In the previous picture, you can see that for Release Version, sys_link.cmd is excluded and sys_link_release.cmd is used.
In the Debug Version it is the opposite. sys_link.cmd is used and sys_link_release.cmd is excluded.
So as summary, I'm able to download your code. I'm not sure how to test what it is doing.
Please read carefully and let me know the result.https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/312/2402.sys_5F00_link_5F00_release.cmdhttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/312/4011.sys_5F00_link.cmd
