Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

I see, years ago, I have used a similar "funclets" method on 68HC11. So, gaps in TCK should not be a problem. BTW, I also noticed that the supply from the LPT FET box is on the low side for flashing (2.8V, 2.7 is the minimum required), so I connected an external 3.3V supply, but no difference. The

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

Am 16.08.2016 um 08:59 schrieb MarkoC: > Next, I checked the TCK pin witn an o'scope, and found out the follwing: > The clock, when running, has a period between 4 and 9 us. If you are referring to the parallel port JTAG; the original MSP430.dll as well as MSP430mspgcc.dll do not supply the fla

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

Hello, I have looked into the ELF file, and there is good code at 0x1100. Also, using an Olimex header board, that I also bought long ago, I could see some code at 0x1100 before erasing it, so the memory is there. Next, I checked the TCK pin witn an o'scope, and found out the follwing: The clock,

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

Hello, thanks to all that have replied, I will be able to dig into this now. I'll try to check the clock too, to see if I have to buy a new interface... I bought this one a LONG time ago, and now had to resurrect an old laptop, to have LPT port at all! Marko -- View this message in context: h

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

On Thu, Aug 11, 2016 at 04:54:18AM -0700, MarkoC wrote: > mc@bpc2 ~/MSP430/MSP-FET $ mspdebug pif -j -d /dev/parport0 > MSPDebug version 0.22 - debugging tool for MSP430 MCUs >From the output, it doesn't look like there's anything wrong obviously wrong with your ELF file, but one thing to be aware

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

It has been a while but I seem to remember having a similar problem. Too long ago to remember details but I think it was a problem with the section flags. You can check the flags using msp430-elf-readelf -S XX.elf -- David W. Schultz http://home.earthlink.net/~david.schultz "Life without stock

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

Hello MarkoC, To rule out a problem with the ELF file (it looks like it is OK from the prog output) use the msp430 binutils to disassemble: msp430-objdump --disassemble main.elf That should confirm you have some valid code in your ELF. The flash offsets seem correct for the device you are using

Re: [Mspgcc-users] MSPDebug unable to find 0451:f430

> Hi Gary, > > If your device actually does have a vendor:product ID of 2047:0010, then > you have V3 firmware, and will need to use the V3 DLL from TI: > >http://processors.wiki.ti.com/index.php/MSP_Debug_Stack#Downloads > > Download the "DLL Developers Package", extract and place MSP430.DLL

Re: [Mspgcc-users] MSPDebug unable to find 0451:f430

>From my experience the V3 tilib interface is significantly faster than the V2 uif interface for programming (maybe as much as 10x faster). It's my preferred version now. If you do a firmware update and it appears to brick the UIF, see http://forum.43oh.com/topic/4349-new-msp430f5529-usb-launchpa

Re: [Mspgcc-users] MSPDebug unable to find 0451:f430

On Sun, Nov 24, 2013 at 05:54:31PM -0800, Eric Decker wrote: > is it possible to use the > ver 3 firmware with Linux dev boxes Hi Eric, Yes, it does compile on Linux, but requires patching. Patches for versions 460f and 460g are available here: http://mspdebug.sourceforge.net/tilib.html Che

Re: [Mspgcc-users] MSPDebug unable to find 0451:f430

hi Daniel is it possible to use the ver 3 firmware with Linux dev boxes >From cPhone > On Nov 24, 2013, at 5:22 PM, Daniel Beer wrote: > >> On Sat, Nov 23, 2013 at 01:20:02PM -0800, garyr wrote: >> My OS is XP, Im using the FET430UIF. I've installed MSPDebug according to the >> instructions f

Re: [Mspgcc-users] MSPDebug unable to find 0451:f430

On Sat, Nov 23, 2013 at 01:20:02PM -0800, garyr wrote: > My OS is XP, Im using the FET430UIF. I've installed MSPDebug according to the > instructions for Windows in the FAQ with one exception: > > The libusb-win32 I found is libusb-win32-1.2.6.0.zip. I couldn't find a > libusb0.dll so I extracted

Re: [Mspgcc-users] mspdebug

On 09/26/2013 04:18 PM, Daniel Beer wrote: > On Thu, Sep 26, 2013 at 09:12:50AM -0400, Ian Chapman wrote: >> I have a silly problem. Mspdebug runs and reports :-- >> #mspdebug rf2500 >> MSPDebug version 0.19 - debugging tool for MSP430 MCUs >> Copyright (C) 2009-2012 Daniel Beer >> This is

Re: [Mspgcc-users] mspdebug

On Thu, Sep 26, 2013 at 09:12:50AM -0400, Ian Chapman wrote: > I have a silly problem. Mspdebug runs and reports :-- > #mspdebug rf2500 > MSPDebug version 0.19 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2012 Daniel Beer > This is free software; see the source for copying condition

Re: [Mspgcc-users] mspdebug

On 09/26/2013 08:12 AM, Ian Chapman wrote: > > usbutil: unable to find a device matching 0451:f432 > The first step is to see if anything is there using lsusb. You should see something like: Bus 003 Device 002: ID 0451:f432 Texas Instruments, Inc. eZ430 Development Tool If it is working. Rece

Re: [Mspgcc-users] mspdebug not releasing target after exit

On Thu, Sep 26, 2013 at 1:20 PM, De Valck wrote: > If you are using tilib, have you tried using the latest version > (slac460f)? I used to have the same problem, but it works with this version. > > This release fixes "After calling the status = MSP430_Reset(..); TST line > high", maybe this is re

Re: [Mspgcc-users] mspdebug not releasing target after exit

If you are using tilib, have you tried using the latest version (slac460f)? I used to have the same problem, but it works with this version. This release fixes "After calling the status = MSP430_Reset(..); TST line high", maybe this is related to your problem? On Thu, Sep 26, 2013 at 11:39 AM,

Re: [Mspgcc-users] mspdebug: enable_bsl_access

On Fri, Aug 30, 2013 at 06:23:46PM -0400, Jose Luis Honorato L. wrote: > I'm having trouble setting the "enable_bsl_access" option in mspgcc. I'm > using the rf2500 interface as the debugger for an msp430f5528 uC. I've > tried the following: > >- Adding "enable_bsl_access True" to ~/.mspdebug

Re: [Mspgcc-users] mspdebug: exit status under cygwin

On Wed, Jun 19, 2013 at 08:47:08AM +0200, Hardy Griech wrote: > compiled under cygwin, mspdebug does not return the correct exit status, > i.e. if no FET has been found success is returned. > > Small patch to solve the problem: Hi Hardy, Thanks for this -- just updated the git repository now.

Re: [Mspgcc-users] mspdebug: exit status under cygwin, more information

On 19.06.2013 08:47, Hardy Griech wrote: : > compiled under cygwin, mspdebug does not return the correct exit status, > i.e. if no FET has been found success is returned. : For more information about this behaviour, one can read http://www.sourceware.org/ml/cygwin-patches/2009-q4/msg00028.html H

Re: [Mspgcc-users] mspdebug and olimex-v1

On 04.05.2013 05:53, Daniel Beer wrote: : > I assume this is the latest git version? I've just altered your solution > slightly to keep a timeout for when usb_bulk_read() returns 0 > immediately. Does this patch work for you? Hi Daniel, yes and yes! Many thanks for your efforts. Hardy ---

Re: [Mspgcc-users] mspdebug and olimex-v1

On Fri, May 03, 2013 at 12:59:11PM +0200, Hardy Griech wrote: > I've encountered problems reading data from the target with an olimex-v1 > FET. Writing was ok. > > Turned out (hopefully), that in cp210x.c/usbtr_recv() the function > usb_bulk_read() may legally return 0. > > Modifying the code

Re: [Mspgcc-users] MSPDebug on Windows Xp

On Thu, Dec 06, 2012 at 08:50:47PM -0300, Leonardo Martinez wrote: > I thought that but i don't have the Makefile, where is it? How do i make it? It's included in the mspdebug source package, which you can get from here: http://mspdebug.sourceforge.net/download.html - Daniel -- Daniel Beer

Re: [Mspgcc-users] MSPDebug on Windows Xp

I thought that but i don't have the Makefile, where is it? How do i make it? On Thu, Dec 6, 2012 at 6:51 PM, Daniel Beer wrote: > On Thu, Dec 06, 2012 at 09:10:54AM -0300, Leonardo Martinez wrote: > > I typed mingw-get install mingw32-make in cmd and it installed some > files. > > One of them i

Re: [Mspgcc-users] MSPDebug on Windows Xp

On Thu, Dec 06, 2012 at 09:10:54AM -0300, Leonardo Martinez wrote: > I typed mingw-get install mingw32-make in cmd and it installed some files. > One of them is the make file. > > Then I added to the Enviroment variables the directories: c:\mingw\bin; > c:\MinGW\msys\1.0\bin\ > > So, I typed make

Re: [Mspgcc-users] MSPDebug on Windows Xp

Hi Daniel, I typed mingw-get install mingw32-make in cmd and it installed some files. One of them is the make file. Then I added to the Enviroment variables the directories: c:\mingw\bin; c:\MinGW\msys\1.0\bin\ So, I typed make or make install in cmd line but it doesn't create de mspdebug.exe. I

Re: [Mspgcc-users] MSPDebug on Windows Xp

On Wed, Dec 05, 2012 at 01:19:15PM -0300, Leonardo Martinez wrote: > The first steps for the installation were ok. > The problem is that II am not understanding what i have to do here in these > steps for proper installation: > > >- > >Download the MSPDebug source > code

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

On Mon, Oct 15, 2012 at 10:16:34AM +0200, Michiel Konstapel wrote: > $ git bisect bad > 08cd326e669c49adfa3c60ecc11fe75b2405427b is the first bad commit > commit 08cd326e669c49adfa3c60ecc11fe75b2405427b > Author: Daniel Beer > Date: Fri Jul 6 08:50:44 2012 +1200 > > Fix support for MSP430F2

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

> If you have time to spare, a git bisect would be really helpful. It'll > probably take about half an hour of testing, though. If you have an > up-to-date git repository sitting there, start with: > > git bisect start > git bisect bad v0.20 > git bisect good v0.18 > > After that, you

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

> -Original Message- > From: Daniel Beer [mailto:dlb...@gmail.com] > Sent: Thursday, October 11, 2012 21:48 > To: Michiel Konstapel > Cc: mspgcc-users@lists.sourceforge.net > Subject: Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418 > > On Thu, Oct 11, 2012 at 0

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

On Thu, Oct 11, 2012 at 08:42:37AM +0200, Michiel Konstapel wrote: > > Hi Michiel, > > > > Looks like perhaps I have broken something, though I can't see what it > > might be. Does the first attempt at identification always fail with > > 0.20, and never fail with 0.18? > > That does seem to be th

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

> Hi Michiel, > > Looks like perhaps I have broken something, though I can't see what it > might be. Does the first attempt at identification always fail with > 0.20, and never fail with 0.18? That does seem to be the case: $ sudo ~/bin/mspdebug-0.18 uif -j 'prog build/lnode_msp2/main.ihex' MSPD

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

On Wed, Oct 10, 2012 at 07:47:08AM +0200, Michiel Konstapel wrote: > Trying to open UIF on /dev/ttyUSB0... > Initializing FET... > FET protocol version is 20401000 > Configured for JTAG (2) > Set Vcc: 3000 mV > fet: FET returned error code 4 (Could not find device (or device not > supported)) > fet

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

> -Original Message- > From: Daniel Beer [mailto:dlb...@gmail.com] > Sent: Wednesday, October 10, 2012 01:21 > To: Michiel Konstapel > Cc: mspgcc-users@lists.sourceforge.net > Subject: Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418 > > On Tue, Oct 09, 2012 at 0

Re: [Mspgcc-users] mspdebug 0.20 and MSP430F2418

On Tue, Oct 09, 2012 at 06:13:41PM +0200, Michiel Konstapel wrote: > After updating mspdebug to version 0.20 (from the tinyprod repository), > it seems I can no longer flash any MSP430F2418s, but a '247 works fine. > Attached is the output from 0.18, 0.20 (both with and without -d). > Did something

Re: [Mspgcc-users] mspdebug working with .ihex files but not .elf

On Mon, Sep 24, 2012 at 05:15:10PM -0300, Jose Luis Honorato L. wrote: > The output when programming the ihex binary is the following: > > $ sudo mspdebug rf2500 "prog bin.ihex" > MSPDebug version 0.20 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2012 Daniel Beer > > Trying to open inte

Re: [Mspgcc-users] mspdebug working with .ihex files but not .elf

Hi Daniel, The output when programming the ihex binary is the following: $ sudo mspdebug rf2500 "prog bin.ihex" MSPDebug version 0.20 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 Daniel Beer Trying to open interface 1 on 035 rf2500: warning: can't detach kernel driver: No data avail

Re: [Mspgcc-users] mspdebug working with .ihex files but not .elf

On Mon, Sep 24, 2012 at 01:30:25PM -0300, Jose Luis Honorato L. wrote: > I'm writing a basic UART data logger for the msp-exp430f5529 board, and for > some reason I'm not able to install the generated binary in .elf format > using mspdebug under Ubuntu 12.04.1 LTS. Anyhow, when generating a copy in

Re: [Mspgcc-users] mspdebug tilib on linux

Original-Nachricht > Datum: Fri, 14 Sep 2012 18:57:48 -0500 > Von: Peter Bigot > An: "GCC for MSP430 - http://mspgcc.sf.net"; > > Betreff: [Mspgcc-users] mspdebug tilib on linux > For those who might want to do this (in my case, on 64-bit Fedora 16), > in addition to Daniel's

Re: [Mspgcc-users] mspdebug tilib on linux

On Sun, Sep 16, 2012 at 05:01:22PM -0500, Peter Bigot wrote: > On Sun, Sep 16, 2012 at 3:36 PM, Daniel Beer wrote: > > I wouldn't have thought this was the right thing to do, but then it's up > > to the library to decide. Does the "run" command work without you having > > to press the reset button

Re: [Mspgcc-users] mspdebug tilib on linux

On Sun, Sep 16, 2012 at 3:36 PM, Daniel Beer wrote: > On Fri, Sep 14, 2012 at 06:57:48PM -0500, Peter Bigot wrote: >> For those who might want to do this (in my case, on 64-bit Fedora 16), >> in addition to Daniel's instructions at >> http://mspdebug.sourceforge.net/tilib.html there's a helpful E2

Re: [Mspgcc-users] mspdebug tilib on linux

On Fri, Sep 14, 2012 at 06:57:48PM -0500, Peter Bigot wrote: > For those who might want to do this (in my case, on 64-bit Fedora 16), > in addition to Daniel's instructions at > http://mspdebug.sourceforge.net/tilib.html there's a helpful E2E > thread at > http://e2e.ti.com/support/microcontroller

Re: [Mspgcc-users] MSPDebug version 0.20 - code "donation"

On Thu, Aug 16, 2012 at 10:22:51PM +0200, Hardy Griech wrote: > may I make some minor code "donations"? > > For me "hexout" does not have enough features, because I'm using a "big" > MSP430. Therefor I need correct address extensions. My implementation > of hexout looks like this: ... > It als

Re: [Mspgcc-users] MSPDebug version 0.20

On 16.08.2012 21:43, Daniel Beer wrote: : > I don't have gcc-3 set up, but are you able to find the definition of > WINAPI anywhere in the Cygwin-included header files? I'm surprised that > this is apparently defined, but not correctly. Hi Daniel, WINAPI is defined as __stdcall in windef.h which

Re: [Mspgcc-users] MSPDebug version 0.20 - code "donation"

Hi Daniel, may I make some minor code "donations"? For me "hexout" does not have enough features, because I'm using a "big" MSP430. Therefor I need correct address extensions. My implementation of hexout looks like this: int cmd_hexout(char **arg) { char *off_text = get_arg(arg);

Re: [Mspgcc-users] MSPDebug version 0.20

On Thu, Aug 16, 2012 at 01:00:01PM +0200, Hardy Griech wrote: > One more thing with tilib: > > > hardy:~/workspace.37/mspdebug> ./mspdebug tilib -d COM12 > MSPDebug version 0.20 - debugging tool for MSP430 MCUs > : > (mspdebug) setbreak 0xa800 > Set breakpoint 0 > (mspdebug) delbreak > Clearing

Re: [Mspgcc-users] MSPDebug version 0.20

On Thu, Aug 16, 2012 at 09:46:55AM +0200, Hardy Griech wrote: > On 14.08.2012 23:00, Daniel Beer wrote: > : > >> One "funny" remark from my side: mspdebug would have been compilable out > >> of the box under cygwin, if I'd used the "correct" compiler: gcc-4 > >> (4.5.3) produces invalid (?) code wh

Re: [Mspgcc-users] MSPDebug version 0.20

One more thing with tilib: hardy:~/workspace.37/mspdebug> ./mspdebug tilib -d COM12 MSPDebug version 0.20 - debugging tool for MSP430 MCUs : (mspdebug) setbreak 0xa800 Set breakpoint 0 (mspdebug) delbreak Clearing all breakpoints... (mspdebug) run tilib: MSP430_EEM_SetBreakpoint: Invalid paramet

Re: [Mspgcc-users] MSPDebug version 0.20

On 14.08.2012 23:00, Daniel Beer wrote: : >> One "funny" remark from my side: mspdebug would have been compilable out >> of the box under cygwin, if I'd used the "correct" compiler: gcc-4 >> (4.5.3) produces invalid (?) code which makes mspdebug crash with >> segmentation fault (with gdb one can se

Re: [Mspgcc-users] MSPDebug version 0.20

On Tue, Aug 14, 2012 at 10:35:39PM +0200, Hardy Griech wrote: > Hey, that came just in time! > > One "funny" remark from my side: mspdebug would have been compilable out > of the box under cygwin, if I'd used the "correct" compiler: gcc-4 > (4.5.3) produces invalid (?) code which makes mspdebug

Re: [Mspgcc-users] MSPDebug version 0.20

Hey, that came just in time! One "funny" remark from my side: mspdebug would have been compilable out of the box under cygwin, if I'd used the "correct" compiler: gcc-4 (4.5.3) produces invalid (?) code which makes mspdebug crash with segmentation fault (with gdb one can see that "device" is ch

Re: [Mspgcc-users] mspdebug fr5739 fuse blown new behavior

No, unfortunately, because the vector values are relative to an expected base at 0xff80. For a self fix, use this commit: http://mspgcc.git.sourceforge.net/git/gitweb.cgi?p=mspgcc/gcc;a=commit;h=0594213396817815f584efe3257987e704b4f187 As best I recall that's the only change necessary. Simpler,

Re: [Mspgcc-users] mspdebug fr5739 fuse blown new behavior

So if someone wanted to fix this themselves, they would just update the ldscript vector address: vectors : ORIGIN = 0xffc0, LENGTH = 0x0040 and change the offsets for the interrupts vectors in the msp430fr5739.h to start at 0xffc0 instead of 0xff80? so the last vector would have an offset 0x3E

Re: [Mspgcc-users] mspdebug fr5739 fuse blown new behavior

On Wed, Jul 4, 2012 at 5:48 PM, Daniel Beer wrote: > On Wed, Jul 04, 2012 at 07:08:15AM -0500, Peter Bigot wrote: >> *) I'm using the trunk version of mspdebug, which I see had a commit back in >>March to remove a step thought to make the "fuse blown" error more >>likely. Most of my devel

Re: [Mspgcc-users] mspdebug fr5739 fuse blown new behavior

On Wed, Jul 4, 2012 at 7:08 AM, Peter Bigot wrote: > I really like the EXP430FR5739 "Fraunchpad", but it has too frequently run > into the "fuse blown" problem when using mspdebug rf2500 load to program it. > I programmed http://dbindner.freeshell.org/msp430/fram_bsl.html into an old > G2211 Launc

Re: [Mspgcc-users] mspdebug fr5739 fuse blown new behavior

On Wed, Jul 04, 2012 at 07:08:15AM -0500, Peter Bigot wrote: > *) I'm using the trunk version of mspdebug, which I see had a commit back in >March to remove a step thought to make the "fuse blown" error more >likely. Most of my development on this platform was before that version. >I d

Re: [Mspgcc-users] MSPDebug Segmentation Fault

On Sat, May 5, 2012 at 10:14 AM, Sergio Campamá wrote: > That's weird, because I used the libusb version mentioned in the FAQ… > And the majority of the people were indeed able to use mspdebug. It just > happened to > 2 guys (I know I said 1 at first, but another one sent me an email). > > Using

Re: [Mspgcc-users] MSPDebug Segmentation Fault

That's weird, because I used the libusb version mentioned in the FAQ… And the majority of the people were indeed able to use mspdebug. It just happened to 2 guys (I know I said 1 at first, but another one sent me an email). Using cygwin to build the git version, I wouldn't need mingw nor libusb?

Re: [Mspgcc-users] MSPDebug Segmentation Fault

At Fri, 4 May 2012 20:26:20 -0400, Sergio Campamá wrote: > Daniel, this is the output of mspdebug when it faults… (disregard the BEGIN, > END parts) > > ==BEGIN > $ mspdebug rf2500 erase 'prog ejemplo.elf' > MSPDebug version 0.19 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2012 Daniel B

Re: [Mspgcc-users] MSPDebug Segmentation Fault

Daniel, this is the output of mspdebug when it faults… (disregard the BEGIN, END parts) ==BEGIN $ mspdebug rf2500 erase 'prog ejemplo.elf' MSPDebug version 0.19 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 Daniel Beer This is free software; see the source for copying conditions. The

Re: [Mspgcc-users] MSPDebug Segmentation Fault

It was the latest version, 0.19, downloaded as a tar.gz file from SF. I'll get you the elf file (although the whole firmware that was compiled is the 6 lines below, compiled with the latest mingw version of mspgcc) and the output. #include int main(){ P1DIR = BIT6+BIT0; P1OUT=B

Re: [Mspgcc-users] MSPDebug Segmentation Fault

At Fri, 4 May 2012 09:07:11 -0400, Sergio Campamá wrote: > Is there any known issues where MSPDebug in Windows (compiled in > cygwin with mingw and ran with cygwin) would throw a segmentation > fault when issuing "mspdebug.exe rf2500 erase 'prog bin.elf' "? If > not, what could be the problem? I ha

Re: [Mspgcc-users] mspdebug tilib v3 update error

Original-Nachricht > Datum: Wed, 21 Mar 2012 10:46:41 +1300 > Von: Daniel Beer > An: "qbert biker" > CC: mspgcc-users@lists.sourceforge.net > Betreff: Re: [Mspgcc-users] mspdebug tilib v3 update error > At Mon, 19 Mar 2012 15:18:28 +0100, qbe

Re: [Mspgcc-users] mspdebug tilib v3 update error

At Mon, 19 Mar 2012 15:18:28 +0100, qbert biker wrote: > > That's correct, although the patch you've linked to may not work > > correctly for 64-bit systems. A better fix would be to change the > > argument type of getTiFileBytes from size_t * to uint32_t *. > > I'm very late but I just discovered

Re: [Mspgcc-users] mspdebug tilib v3 update error

Original-Nachricht > Datum: Mon, 13 Feb 2012 10:26:11 +1300 > Von: Daniel Beer > An: "GCC for MSP430 - http://mspgcc.sf.net"; > > Betreff: Re: [Mspgcc-users] mspdebug tilib v3 update error > On Sun, Feb 12, 2012 at 04:10:12PM +0200, Andres Vahter

Re: [Mspgcc-users] mspdebug: resetting target

At Wed, 7 Mar 2012 15:15:30 -0800, wayne roberts wrote: > I have set a breakpoint at main(), and confirmed the msp430 is running from > reset vector after "monitor reset" then "continue".  (it halts at main again) > > Yet, I am also using gdb on another platform, where i can single step after >

Re: [Mspgcc-users] mspdebug: resetting target

At Wed, 07 Mar 2012 22:04:50 +0100, Chris Liechti wrote: > i was just thinking about that. maybe the server could send a packet > with register update on "monitor reset". > > unfortunately, it looks like "Stop Reply Packets" ("T") are not expected > when monitor commands are issued, at least there

Re: [Mspgcc-users] mspdebug: resetting target

At Tue, 6 Mar 2012 18:51:26 -0800, wayne roberts wrote: > (gdb) bt > #0 0x in ?? () > #1 0xc0c0 in blah,blah..etc.. > (gdb) monitor reset > (gdb) n > Cannot find bounds of current function > (gdb) > > So, when i issue monitor reset, should the program counter and stack > pointer be r

Re: [Mspgcc-users] MSPDebug version 0.19

On 03/mar/2012, at 13:41, Matthias Hartmann wrote: > You may download a windows mingw32 build here. > > url:http://www.mydrive.ch/login > user: guest@Hutch67 > pw: mspgcc4!mingw32 > > Matthias > > Am 03.03.2012 00:09, schrieb Daniel Beer: >> MSPDebug version 0.19 is available from: >> >> h

Re: [Mspgcc-users] MSPDebug version 0.19

You may download a windows mingw32 build here. url:http://www.mydrive.ch/login user: guest@Hutch67 pw: mspgcc4!mingw32 Matthias Am 03.03.2012 00:09, schrieb Daniel Beer: > MSPDebug version 0.19 is available from: > > http://mspdebug.sourceforge.net/download.html > > New in this release: > >

Re: [Mspgcc-users] mspdebug tilib v3 update error

Wait a minute, It does not work with IAR and CCS anymore. I can downgrade/upgrade it with those tools, however I cannot download software and debug. With my other FET it works. I guess problem started if SmartRF Studio also upgraded FET firmware. Have to check from TI forums. Andres On 18.02.2

Re: [Mspgcc-users] mspdebug tilib v3 update error

Hi, I tried that: downgraded to V2 with windows utilities because I do not have V2 image saved and I wanted to save it just in case. With V2 firmware I moved to mspdebug (git version): >mspdebug uif-bsl -d /dev/ttyUSB16 "hexout 0x2500 0xdb00 old-v2-firmware.hex" MSPDebug version 0.18 - debugging

Re: [Mspgcc-users] mspdebug tilib v3 update error

On Sun, Feb 12, 2012 at 04:10:12PM +0200, Andres Vahter wrote: > I am having some trouble with the latest tilib. > I got lib from: http://www-s.ti.com/sc/techzip/slac460.zip. Actually the file > is now called slac460a.zip. > > It seems like patches mentioned here are not required anymore > http:

Re: [Mspgcc-users] mspdebug fet identity failed error Launchpad 2553

On Thu, Feb 09, 2012 at 12:04:03PM -0600, Yamaplos . wrote: > to my utter surprise, getting the Launchpad to interact with a vanilla > OLPC XO is very easy. > http://processors.wiki.ti.com/index.php/OLPC_XO-1 > > However, I do get a >fet: identity failed > when I use a /vanilla/ Launchpad (now

Re: [Mspgcc-users] MSPDebug and MinGW

ot; ; "mspgcc-users@lists.sourceforge.net" Sent: Tuesday, 31 January 2012, 11:10 Subject: Re: [Mspgcc-users] MSPDebug and MinGW On Mon, Jan 30, 2012 at 06:03:06PM -0800, jcs...@yahoo.com wrote: > Calling mspdebug -j uif also didn't help. >   > D:\Utilities\msp430-tools for Windows u

Re: [Mspgcc-users] MSPDebug and MinGW

On Mon, Jan 30, 2012 at 06:03:06PM -0800, jcs...@yahoo.com wrote: > Calling mspdebug -j uif also didn't help. >   > D:\Utilities\msp430-tools for Windows using MingW\mspdebug\mspdebug-0.18- > mingw32>mspdebug -j uif > MSPDebug version 0.18 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2011

Re: [Mspgcc-users] MSPDebug and MinGW

.com Cc: "matthiashart...@versanet.de" ; "mspgcc-users@lists.sourceforge.net" Sent: Tuesday, 31 January 2012, 4:56 Subject: Re: [Mspgcc-users] MSPDebug and MinGW On Mon, Jan 30, 2012 at 01:41:58AM -0800, jcs...@yahoo.com wrote: > Placing a copy of libusb0.dll in the same

Re: [Mspgcc-users] MSPDebug and MinGW

e file specified. By the way, I am running on Windows XP Pro SP3. thank you Regards, jing > Date: Mon, 30 Jan 2012 07:50:15 +0100 From: Matthias Hartmann Subject: Re: [Mspgcc-users] MSPDebug and MinGW To: mspgcc-users@lists.sourceforge.net Message-ID:<4f263da7.4000...@versanet.de>

Re: [Mspgcc-users] MSPDebug and MinGW

On Mon, Jan 30, 2012 at 01:41:58AM -0800, jcs...@yahoo.com wrote: > Placing a copy of libusb0.dll in the same folder as mspdebug.exe doesn't work > regardless where I invoke the application (windows command prompt or mingw). > The same timeout error occurs "uif: read error: The wait operation time

Re: [Mspgcc-users] MSPDebug and MinGW

y; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > Trying to open UIF on COM7... > uif: can't open serial device: COM7: The system cannot find the file > specified. > By the way, I am running on Windows XP Pro SP3. > > > thank you > Regards, > jin

Re: [Mspgcc-users] MSPDebug and MinGW

l device: COM7: The system cannot find the file specified. By the way, I am running on Windows XP Pro SP3.     thank you Regards, jing   > Date: Mon, 30 Jan 2012 07:50:15 +0100 > From: Matthias Hartmann > Subject: Re: [Mspgcc-users] MSPDebug and MinGW &g

Re: [Mspgcc-users] MSPDebug and MinGW

om: Daniel Beer To: jing Cc: mspgcc-users@lists.sourceforge.net Sent: Saturday, 28 January 2012, 10:49 Subject: Re: [Mspgcc-users] MSPDebug and MinGW On Fri, Jan 27, 2012 at 08:28:47AM +, jing wrote: Have you manage to make use of mspdebug on mingw? I tried with the latest v0.18 but is gettin

Re: [Mspgcc-users] MSPDebug and MinGW

... uif: read error: The wait operation timed out. fet: open failed Regards, Jing From: Daniel Beer To: jing Cc: mspgcc-users@lists.sourceforge.net Sent: Saturday, 28 January 2012, 10:49 Subject: Re: [Mspgcc-users] MSPDebug and MinGW On Fri, Jan 27, 2012 at 08

Re: [Mspgcc-users] MSPDebug and MinGW

On Fri, Jan 27, 2012 at 08:28:47AM +, jing wrote: > Have you manage to make use of mspdebug on mingw? > > I tried with the latest v0.18 but is getting the same timeout error you'd > encounter. (running windows xp) > > FET is definitely working as i was able to program my msp430 experimenter

Re: [Mspgcc-users] MSPDebug and MinGW

Hello Matthias, Have you manage to make use of mspdebug on mingw? I tried with the latest v0.18 but is getting the same timeout error you'd encounter. (running windows xp) FET is definitely working as i was able to program my msp430 experimenter board using MSP430Flasher_v1.1.5.0. thank yo

Re: [Mspgcc-users] mspdebug / FET v2 / 5528

Hi Daniel thanks for the hints. I gave the package a quick spin and found the fix for the getTiFileBytes method in your "older" patch package. It gets to the linking part and fails there (as you said) as it assumes a linux environment. I can fix that. I'll try updating to v3 next, to see, if t

Re: [Mspgcc-users] mspdebug / FET v2 / 5528

On Tue, Jan 17, 2012 at 10:54:16AM +0100, Matthias Ringwald wrote: > A slightly different topic: did anyone use the MSP430.dll v3 on Mac > successfully (mspdebug site and some google-ing didn't suggest an answer). I know of one person who's currently trying to get it working. If you want to exper

Re: [Mspgcc-users] mspdebug / FET v2 / 5528

Hi Wayne thanks for the reply. In my case, it resolved itself. I get the mspdebug command prompt with the v2 driver. I'm curious, if I can reproduce this problem. A slightly different topic: did anyone use the MSP430.dll v3 on Mac successfully (mspdebug site and some google-ing didn't suggest

Re: [Mspgcc-users] mspdebug / FET v2 / 5528

Hi Matthias, I had a similar problem with an MSP430F5437 part (it failed C_IDENT3). Using the latest version of mspdebug and the new MSP430.dll v3 driver and firmware has fixed the problem. I hope it also works for you. - Wayne -Original Message- From: Matthias Ringwald [mailto:matth

Re: [Mspgcc-users] Mspdebug and Olimex JTAG Tiny V2

On Sun, Dec 25, 2011 at 02:36:16AM +0100, Christof Petig wrote: > it took me some time to figure out how to use an Olimex JTAG Tiny V2 > because, under Linux, it behaves so much differently than the previous > version. > > The new device type will easily provide a serial port via cdc_acm (USB > co

Re: [Mspgcc-users] Mspdebug and Olimex JTAG Tiny V2

On So, 2011-12-25 at 02:36 +0100, Christof Petig wrote: > The included patch will make a V2 work - at the cost of probably > destroying V1 serial support. sorry, evolution insisted on base64 coding it - so it got stripped by the mailing list. Here it is: diff --git a/drivers/uif.c b/drivers/uif.c

Re: [Mspgcc-users] MSPDebug version 0.18

Am Sonntag, den 20.11.2011, 11:16 +0100 schrieb Stephan Goldenberg: > The firmware is missing. > > oppa@oppa-mag:~$ locate ti_usb-3410.bin > oppa@oppa-mag:~$ fw-detect > Detected driver that requires firmware to operate > - > > # > # There i

Re: [Mspgcc-users] MSPDebug version 0.18

On Sun, Nov 20, 2011 at 11:16:11AM +0100, Stephan Goldenberg wrote: > Am Samstag, den 19.11.2011, 16:57 -0300 schrieb Sergio Campamá: > > Hello, sorry to interrupt, but I have a (maybe) similar problem. I also > > have the 1.4a JTAG programmer, and when I connect it to Ubuntu (11.04), it > > says

Re: [Mspgcc-users] MSPDebug version 0.18

Got it working now, it was a problem with the TI3410 driver for mac and VMWare. Thanks! --- Sergio Campamá sergiocamp...@gmail.com On Nov 20, 2011, at 7:16 AM, Stephan Goldenberg wrote: > Am Samstag, den 19.11.2011, 16:57 -0300 schrieb Sergio Campamá: >> He

Re: [Mspgcc-users] MSPDebug version 0.18

Am Samstag, den 19.11.2011, 16:57 -0300 schrieb Sergio Campamá: > Hello, sorry to interrupt, but I have a (maybe) similar problem. I also have > the 1.4a JTAG programmer, and when I connect it to Ubuntu (11.04), it says > that the firmware couldn't be downloaded. > > The Launchpads I have run pe

Re: [Mspgcc-users] MSPDebug version 0.18

Hello, sorry to interrupt, but I have a (maybe) similar problem. I also have the 1.4a JTAG programmer, and when I connect it to Ubuntu (11.04), it says that the firmware couldn't be downloaded. The Launchpads I have run perfectly, but the UIF won't even show as /dev/ttyUSB0. The actual output

Re: [Mspgcc-users] MSPDebug version 0.18 oops

Am Dienstag, den 15.11.2011, 08:43 +1300 schrieb Daniel Beer: > Hi Stephan, > > It looks like you now have V3 firmware, which requires using the TI > MSP430 library via the "tilib" driver. You can downgrade to V2 again > by following the instructions here: > > http://processors.wiki.ti.com/in

Re: [Mspgcc-users] MSPDebug version 0.18 oops

On Mon, Nov 14, 2011 at 06:51:15PM +0100, Stephan Goldenberg wrote: > Sory, forgot two things. > > > Hi Stephan, > > > > What shows up if you run "dmesg" after plugging the device in? Perhaps > > you are missing the kernel driver or the firmware image for the > driver. > > Yes, there seems to be

Re: [Mspgcc-users] MSPDebug version 0.18 oops

Sory, forgot two things. > Hi Stephan, > > What shows up if you run "dmesg" after plugging the device in? Perhaps > you are missing the kernel driver or the firmware image for the driver. Yes, there seems to be some action/communication. > > Am I right in guessing that there's a delay before e

Re: [Mspgcc-users] MSPDebug version 0.18

> Hi Stephan, > > What shows up if you run "dmesg" after plugging the device in? Perhaps > you are missing the kernel driver or the firmware image for the driver. > > Am I right in guessing that there's a delay before each error message > shows up? > > - Daniel > Hi, good idea. Why didn't I c

  1   2   3   4   >