Search the Community
Showing results for tags 'BSL'.
Found 9 results
-
Hi, I am trying to invoque the BSL with the following code : #define BSL_PARAM 0xFC48FFFF // I2C slave address = 0x48, Interface selection = Auto #define BSL_API_TABLE_ADDR 0x00202000 // Address of BSL API table #define BSL_ENTRY_FUNCTION (*((uint32_t *)BSL_API_TABLE_ADDR)) ((void (*)())BSL_ENTRY_FUNCTION)((uint32_t)BSL_PARAM); // Call the BSL with given BSL parameters It compiles fine when I use this code inside a C project (like the uartecho exaple) However, when I use it inside a Energia project in CSS, I get the error "Too many arguments to function" on this line ((v
-
Last summer I worked on the idea of embedding a USB-to-Serial adapter in Value Line projects so firmware revisions could be done with only a USB cable and the right software, without needing a Launchpad. The adapter chips and modules containing them are now so inexpensive that this makes sense. On the chance that it might be useful to someone, I've written it all up and posted it to Github: https://github.com/gbhug5a/MSP430-BSL The project is summarized in the README, and explained in detail, with needed software and hardware, in the PDF.
-
I have a G2553 set up on a breadboard, and am using a USB-to-UART adapter for BSL flashing. TI provides BSLDEMO2.exe on the Windows side to do the flashing, but I've been unable to get it to work. If I use the special signalling pattern on /RST and Test, I get a "synchromization failed" error, and if I boot directly into the cold start vector of BSL, I get a "communications error". So I just wondered if anyone here has actually done this successfully? The two ends talk to each other, but it always errors out.
-
[Edit: after posting this, I found out I needed to use the rom-bsl driver for mspdebug. That works!] [Edit 2: after a reboot, I no longer have to do anything to toggle the RTS line.] I have a tube of old MSP430F1232 bare chips in the SOIC-28 package, and I thought I'd make an attempt to flash one using a USB CP2102 serial adapter. However, I haven't been able to flash the chip yet. The TEST and /RST pins are connected to RTS and DTR, respectively. Comparing my scope trace with the timing diagram in SLAU319L Figure 2, the sequence looks right. However, mspdebug reports
-
Why on earth would TI engineers use random GPIO pins for the built-in UART BSL instead of RXD/TXD of one of the USCI peripherals?? I mean, in 90% of real world use cases, the likely source of a firmware update, i.e. computer, USB bridge, blue-tooth modem etc., will be hanging on one of the UARTs. Instead they picked 2 pins on the side of the package where all the I/Os are nicely lined up and which therefore most likely would be wired up to all the other stuff. Oh yes, and of course those two pins are exactly on the opposite side of the TEST / BSL enable pin. /rant
-
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
-
Hi, We need some advice on updating MSP430F5529 program using USB BSL. We want to add/update a small part of data to the current firmware through USB BSL. But the problem is the BSL automatically performs a mass erase, TI's Appl note(SLAA452B) mentions that the BSL password reside at addresses 0xFFE0 to 0xFFFF which changes for every new program and fixing the ISR locations solves the problem of MASS Erase. But we don't know how exactly do we Fix the ISR locations. Could you please let me know if there is a reference or example on how to Fix the MSP430 ISR locations. Regar
-
hey people, i am new to the msp430 family and, as the title reads, i am trying to program a simple blinky bin(txt) created with ccs on a g2955. here is the catch, i dont have access to any of the regular tools you guys use(fets and stuff), because of where i live. in fact im using the 430 because of TI`s very generous sample program. i am using a com to 3v3 adapter similar to this one but im having a hard time finding software to do the upload. i read this post where it says that its possible to do with mspdebug. thing is i could not compile it on ubuntu (i get a 404 when trying to install
