View previous topic :: View next topic |
Author |
Message |
spilz
Joined: 30 Jan 2012 Posts: 219
|
ccsbootloader.exe error when load program.hex |
Posted: Wed Nov 07, 2012 6:51 am |
|
|
Hi everybody,
I'm working on a project with boot loader and I have a problem too load the program in the chip so I need your help
- I load the usb bootloader in the chip with a programer, it works well.
- When I charge the new program.hex by the bootloader with Siow.exe, the program is completly downloaded and works well. (this part is ok)
I try to build the easiest way to load new program for people who don't know electronic.
So instead of using Siow.exe, I want to use ccsbootloader.exe with the command :
"ccsbootloader PORT=COM1 BAUD=19200 program.hex"
Problem :
The program is downloaded until I receive an error message
"Output buffer too small for block."
Does someone know from where does that error come ?
and how to solve it?
Thanks For your help |
|
|
spilz
Joined: 30 Jan 2012 Posts: 219
|
|
Posted: Wed Nov 07, 2012 6:54 am |
|
|
more precisions :
If program.hex is small ("hello word" program)
- it is downloaded properly by Siow.exe (and works well)
- it is downloaded properly by the command ccsbootloader.exe (and works well)
If program.hex is big
- it is downloaded properly by Siow.exe (and works well)
- I get the error with ccsbootloader.exe |
|
|
mcclmar
Joined: 03 Feb 2014 Posts: 1
|
getting ccsbootloader.exe to work |
Posted: Mon Feb 03, 2014 6:56 pm |
|
|
Hi spilz,
Sorry to dig up an old thread, but did you have any luck getting ccsbootloader.exe to work?
I may be having the same issue you had. I can always load programs successfully using SIOW but ccsbootloader only works maybe 20% of the time.
thanks |
|
|
spilz
Joined: 30 Jan 2012 Posts: 219
|
|
Posted: Tue Feb 04, 2014 1:14 am |
|
|
hello,
I don't really remember, but I think the issue came from my USB port (i'm using a MacBook Pro with Seven). One of the both USB port works well, the other one had some issue (it seems it's a power issue).
try it
spilz |
|
|
spilz
Joined: 30 Jan 2012 Posts: 219
|
|
Posted: Tue Sep 23, 2014 6:13 am |
|
|
Hello,
I don't know why, but adding : DEBUGT=out.txt
in the command line seems to solve this issue... |
|
|
|