Another question for propeller programmers

4x5n

As most already know I'm new to using the propeller and have jumped in head first! I've been looking at viewport and am wondering how many people here are using it and if so how are you using it. More then once I've wished for a debugger that would allow me to single step code, set breakpoints, etc.

Zap-o

I am sure viewpoint is nice but honestly I learned from making my own debugger/s. Often I will just write an object in my code that will output some (the debug) data to a 20x4 LCD, USB to a computer program or light up some LEDs. It is a great way to learn and debug your programs at the same time.

prof_braino

I haven't used viewport yet, as I am not to the point where I need those functions and need to buy the software. But it is pretty cool and does neat stuff, so its on the short list.

In the mean time, the forth option provides a slightly different paradigm, and does may of the same functions. Propforth does not need a PC, it runs directly on the prop and only needs a terminal, so the smallest netbook that can run a terminal emulation progrma is sufficient. It has a software logic analyzer that can sample at every clock cycle to cog memory, or every 40 cycles to main memory. One can execute individual functions and thus step through code. The code can be modified and saved without having to run prop tool or recompile spin. It does a bunch of other stuff like in line assembler, scripting allowing programs to the size of SD memory, and its free. I have found that I really don't need anything else until things get REALLY complex. Of course forth is not the "popular" option which would be C.

smbaker

I use viewport quite frequently. I used to always implement a composite TV output on my boards for debugging (I suppose serial debugging would have been an obvious alternative), but I've found it's much more convenient to watch variables with viewport. You also gain the benefit of a built-in logic analyzer, graphing of your variables, the ability to edit a variable on the fly.

I wish viewport and Propeller Tool were more tightly integrated. I really like the editor and compiler in Propeller Tool, and I find myself constantly saving and then load/executing the code in viewport.

(now I'm starting to feel a bit spoiled complaining about having to save a file in one tool and load it in another; I remember the days when a compile-test-revise cycle involved not only separate tools, but EEPROM erasers, programmers, and ZIF sockets)

smbaker

I use viewport quite frequently. I used to always implement a composite TV output on my boards for debugging (I suppose serial debugging would have been an obvious alternative), but I've found it's much more convenient to watch variables with viewport. You also gain the benefit of a built-in logic analyzer, graphing of your variables, the ability to edit a variable on the fly. Single-stepping/breakpoints isn't something I've done on the prop, nor is it something I've needed (I didn't even know viewport did this!).

I wish viewport and Propeller Tool were more tightly integrated. I really like the editor and compiler in Propeller Tool, and I find myself constantly saving and then load/executing the code in viewport.

(now I'm starting to feel a bit spoiled complaining about having to save a file in one tool and load it in another; I remember the days when a compile-test-revise cycle involved not only separate tools, but EEPROM erasers, programmers, and ZIF sockets)

StefanL38

There are two other debbugers that are freeware PASD from insonix (Ariba) and a a multi-cog debugger quite famous too - I'm really sorry - I don't remember the author
keep the questions coming
best regards

Stefan

Hanno

Hi!
Welcome to the Propeller! ViewPort gives you lots of debugging tools- including Visual Studio like line by line stepping, breakpoint, memory view, profiler... See here for a review from Robot magazine:
http://www.parallax.com/Portals/0/Downloads/docs/article/ROBOT_ViewPort.pdf
Let me know if you need any help...
Hanno