Jump to content


  • Content Count

  • Joined

  • Last visited

About vin43

  • Rank
    Noob Class

Profile Information

  • Gender
  • Location
  1. @all: I wanted to ask about DLL. I read about the MSP debug stack and how it is important (giving the interface between the PC software and the target MCU). I have read about the FET, which we use and how it gets updated if it doesnt have the latest drivers. I wanted to know little about the DLLs. I know this is off-topic. Since I'm trying to understand more about the debug world it is good to know what exactly the DLLs do? I have read the wiki ( http://processors.wiki.ti.com/index.php/MSP_Debug_Stack ) . It has been mentioned they have been written in C++. So I downloaded the DLL Developers Package v3.4.3.4 to know what it contains. It has the HIL.dll and msp430.dll. Are these the once which we can also see in the CCS installation folder-> DebugServer->Drivers folder? From my understanding, from the header files in the Include folder (of DLL Package) and the Lib folder, the 2 DLLs (HIL.dll and msp430.dll) are generated. Am I right? Ofcourse, we cannot open the DLLs in Notepad++, its unreadable! Thank you! Regardsm Vin43
  2. @@roadrunner84 @ Rickta59 and @@spirilis : thanks for the inputs! I will try to gain some more knowledge and get back to it later! I will try to use the BSL of the launchpad which I have. Lets see! thanks!
  3. @jazz: thanks for the reply. I had read very roughly the 2 documents before posting this question. The docs give the details. However, I wanted to know the overall significance of the different downloading/debugging/firmware-update mechanisms and how and when are they mostly used depending whether the controller is under-development phase or in the customer side. Thanks. I will try to get more info regarding this topic. Regards, Vin43 "thank you"
  4. thanks for your inputs. I wanted little more clarification and info regarding burning the chip/debugging. As a new to microcontroller usage, I have below points: Please enlighten me with you experience. Googling is ineffective in these questions! 1. In cheap-launchpads (LP), we have In-circuit-debugger: where we just connect the LP to the PC via the USB and everything (downloading the hex, debugging) is done by the In-circuit debugger. Then why cant we have in-circuit debuggers on all development kits? 2. I had a microcontroller-kit, with pin-outs on all the pins (used in development/testing) where we can drop in the chip and download/debug the code using the external FET (flash emulation tool). Why is it called so? It emulates the controller?(debugging?) historically, controller memories were flash, so it is called FET, is it? What are the advantages/differences of using FET 3. JTAG (4 wire) is another way to download the hex into the controller. significance of JTAG? How is it helpful? In MSP the PJ port pins have the JTAG as secondary functions and by-default, the PJ pins are used as GPIOs. Then how to use them for JTAG. I know the PJSELx settings, but I wanted to know how is it connected to the PC? TDO,TDI, TMS, TCK. 4. SBW (2 wire) saves 2 pins. Similar to JTAG? 5. Among all these, how the BSL is significant? you said no external devices are needed. Just the PC and UART connection right?. It offers more control than other methods? It is said, we can 'hack' the device through BSL! Is it? Please share your experiences and knowledge. I'm very new to the controller-world. I just use the MSP430 kits and write the code. I generally dont have to worry much on these issues, but I wanted to understand these points better. I'm also googling about them. Many thanks :-) Regards Vin43
  5. Hello all, I have been trying to understand the importance of the BSL. From the TI doc, "Programming with the BSL" I realize that BSL is used to access Memory, during the different phases of the controller. My question is: why do we need this BSL? is it required to calibrate the controller? like setting the temperature and operating conditions, before the controller takes the program execution address from the reset vector? Generally, from my understanding and usage: we used the JTAG, FET tool to download the code onto the controller, to debug the code. Then why do we need the BSL? Thanks a lot for sharing your experiences! Vin43
  6. Hi chicken Oh, now I understand it. This is so different from FR series. Thanks a lot! ~vin43
  7. Hello all, I'm getting confused with the configuration of the clock in my G2553 device. I tried to find in the forum regarding this post but couldnt clear my doubt. 1.The DCOCTL has DCOx and MODx fields but there is no table in the user guide mentioning the values to be given to these fields to get the required DCO Freq. 2. To get 1Mhz DCO clock I used DCOCTL = CALDCO_1MHZ; BCSCTL1 = CALBC1_1MHZ; and I got 1MHz DCO. 3.When I check the DCOCTL and BCSCTL1 in the debugger the values are DCOCTL = 0xBC BCSCTL1= 0x86 4. It means that there is modulation. I dont know why this modulation. About the calibration, is it to get the operation in the required range of temperature as I found in Data sheet? 5. I'm confortable with FR series where the clock settings is so much easier to understand. Please give your views in clearing this confusion! Thanks in advance. ~ vin43
  • Create New...