jazz 209 Posted September 30, 2012 Share Posted September 30, 2012 This is for assembler programmers, way of debugging based on software without any hardware tools (only uC). So if you are programming MSP430 with C, playing in (launchpad) lego world, this is not for you. I will not publish complete source here, but will introduce idea, and help someone to build it's own version (not only for MSP430). I was working (before MSP430) on some other uC that don't have debugging interface (like MSP430), and there is no nice way for checking the code. There was (for some uC) debugging based on inserting software layer under the user program, or only adding some software around breakpoints. And than this special software inside uC was communicating with debugging hardware, or only with PC application. Big minus for debugging on this (only possible) way was in losing some flash/ram memory blocks, original vector table or registers, because debugger was using them for itself. All uC have (at least one) uart port, or it can be created (by software) if not exist. My idea was to use one uart for uC/PC main application, and another uart for uC/PC debugging. Debugging function are placed in separate file and just in lined in main assembler source (#include "dbg_uart.s43"). If debugging in main file is enabled (#define DBG_UART) also will be enabled all debugging functions (#ifdef DBG_UART). If debugging in main file is disabled, produced program (final release) will be in original form, without any debugging part. I made mine own BLS version, and I use it not only for flashing, but also for standard MSP430/PC uart communication when I need it. It is based on MAX3243E (SOIC) from TI, and placed inside DB9 connector. RobG 1 Quote Link to post Share on other sites
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.