This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ADS1292 FE GUI source code or flow chart

Other Parts Discussed in Thread: ADS1292, MSP430F5529

Could some one guide me on the loading of the MSP firmware when the GUI is started. If i change the source code, which gets installed once the ADS1292 FE EVM software is installed, and store it in the same folder would the changed firmware get loaded? 

Can i get hold of the flowchart of the software of the exe file that is run to load the GUI and firmware on the EVM?

  • Hey Viney,

    The firmware for that EVM is loaded on to the MSP430's flash memory before it's shipped so the EVM software doesn't touch it. To change the firmware, you could always change the source code how you'd like and then re flash it yourself using a generic flash programmer. One disclaimer, though, is that we probably won't be able to help you if the EVM isn't working because of a change you made to the firmware. I'd recommend keeping a copy of the original firmware and binary handy so if your changes prevent you from using the EVM software, you can always go back to the original setup.

    Regards,
    Brian Pisani
  • Brian,

    Thanks. What if i were to do that using the MSP430F5529 LP and the ADS1292  connected to the LP? If I connect the pins on the LP and open the EVM software, there is a button for flasing the firmware. Can I use that route to load the firmware on to the LP and use the combination of LP, ADS1292. Would that work? If not how do I load the firmware in to the LP & ADS1292 combination so that it would work like the EVM. I am asking this as in the source code I see a lot of the files like ADS1x9x.c, ADS1x9x_main.c etc How do I load all of them on to the LP? I may be asking very trivial questions but I am a beginner for these things.

    Regards

    Viney Chaddha

  • Hey Viney,

    I doubt that configuration would work since I suspect the firmware for the EVM uses some of the peripherals on the board besides the ADS1292. Besides, matching the pins exactly from the Launchpad to the EVM board in the firmware might prove to be more trouble than its worth. Another consideration to make would be power. The MSP430 on the EVM board and the ADS1292 use the same digital supplies so considerations would have to be made to use the power supplies from the EVM board but cut the traces on the digital lines between the EVM MSP430 and the ADS1292. Short answer is that it might be possible, but the amount of work it would take to get it to that point would probably not be worth it.

    In terms of the source code, you'll have to tell me if the source code includes a ".bin" file that corresponds to the compiled binary code for the firmware. If it does, you can simply use that file to flash our firmware on to the MSP. If you want to change the source code then flash it, you'll have to compile and build the files yourself. You can do that using Code Composer Studio.

    Regards,
    Brian Pisani
  • Brian,
    I had compared the two, EVM and LP, the difference is the Flash and Battery management, the others are DNI. What if I ignore both of them and make all the commands in the code as "comment" by enclosing every thing in */...../* in their individual source code. The BIN file is not included.

    Thanks for your suggestion on using the modified EVM, I still would lie to go ahead with my plan and try to get the hang of it. I am touching the controller after a long time, >23 years. The last time i had used a Microprocessor was in college and that too the massive boards that needed to be programmed in assembly. Lot of changes since then. I want to get the hang of it and have the first hand experience on it and use that exp to get into IOH (IOT) as my personal startup.
    Regards
    Viney Chaddha
  • Hey Viney,

    Never too late to start back up again!

    I'm not sure if enclosing the lines you've suggested in comments will necessarily make it work right away. It might take some serious debug to make it work. If you're willing to do that and make the changes to the hardware, I say go for it. Like I said before, I recommend keeping copies of the original firmware on file so if something goes awry you can always go back (you can always solder the broken traces back together as well). I'd also advise using revision control software (like Git) for you to store your progressive copies as you go along.

    Since there is no .bin file with the source code, you're going to have to use Code Composer Studio, create a project with your specific microcontroller as the target device, put all the source files in the project, and build it with a binary as the output file type. If you have questions about that process, I'd recommend looking to the Code Composer Studio e2e forum since I am not an expert with CCS.

    Happy coding!
    Brian Pisani