search

dlbeer / mspdebug

Debugging tool for MSP430 MCUs
GNU General Public License v2.0
184 stars 80 forks source link

Slow programming of MSP430F5328 using MSP320-JTAG-TINY-V2 under mspdebug #80

Closed raistlin83 closed 5 years ago

raistlin83 commented 5 years ago

Hi,

I have a problem / question: i'm trying to program a MSP430F5328 chip with quite large TXT file - about 122 kB of code memory.

When i'm using "Olimex MPS Programmer" under win10, everything is ok, whole process takes about 10-12 seconds. But when i tried to do this with mspdebug software under linux, whole process takes about 100 seconds.

MSPDEBUG version is 0.25 Debian 8 on a BeagleBone Black mspdebug -q -j olimex "prog /home/wsad.txt"

Do anyone know how to speed it up? I have to program my chip using mspdebug and almost 2 minutes is definitely too long..

dlbeer commented 5 years ago

On Tue, Nov 27, 2018 at 02:30:24PM +0000, raistlin83 wrote:

I have a problem / question: i'm trying to program a MSP430F5328 chip with quite large TXT file - about 122 kB of code memory.

When i'm using "Olimex MPS Programmer" under win10, everything is ok, whole process takes about 10-12 seconds. But when i tried to do this with mspdebug software under linux, whole process takes about 100 seconds.

MSPDEBUG version is 0.25 Debian 8 on a BeagleBone Black mspdebug -q -j olimex "prog /home/wsad.txt"

Do anyone know how to speed it up? I have to program my chip using mspdebug and almost 2 minutes is definitely too long..

Have a look at the "fet_block_size" option. It's by default set to a small value, but you can increase it as long as you have enough RAM in the device to hold each block.

Cheers, Daniel

-- Daniel Beer dlbeer@gmail.com http://dlbeer.co.nz/ PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B

raistlin83 commented 5 years ago

Thanks Daniel,

after setting the block size to 499:

(mspdebug) opt fet_block_size 499

whole operation lasts about 15 sec :)

raistlin83 commented 5 years ago

Problem solved