• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 79 subscribers
  • Views 136 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430F6775A: Addresses

Peter Peter
Intellectual 270 points
Part Number: MSP430F6775A

Tool/software:

Hi,

I would like to ask what is the first address that will be loaded to PC counter of msp430f6775a and how it will be loaded or from what address?

  • 0
    Guru 21965 points

    Read Chapter 1 of the guide. (SLAU208)

  • 0 in reply to David Schultz
    Intellectual 270 points

    Hi, I cannot see any information about the addresses I have noticed the boot code which should start before BSL but there is no additional information about it like where it is stored. I have noticed that there is mentioned another interrupt vector table in JTAG section of slau but it is in older SLAU for F5 devices only.

  • 0 in reply to Peter Peter
    TI__Genius 9122 points

    Hi, 

    The ROM based bootcode part is not visible to the user.

    The code closest to boot is resethandler.

    Please refer to 1.2.1 Device Initial Conditions After System Reset.

    Regards,

    Helic

  • 0 in reply to Helic Chi
    Intellectual 270 points

    Hi!

    Yes, I have seen it; I was just confused about how the addresses are defined in the custom BSL manual. For example, how are the protection function address and the JTAG lock managed? Specifically, are the addresses and checks, such as verifying if the BSL signature is at a specific address, as well as the JTAG lock and protection function address stored at specific memory locations, all handled by the boot code?

    This boot code is also responsible for loading the settings of the DCO, correct? The boot code itself is not the low-level assembly code that stores the signature, handles the protection functions, or jumps to the main boot function, right? Furthermore, this boot code cannot be modified because it is not visible, is that correct?

    Therefore, the addresses, including the JTAG lock, protection function, and signature, must remain as defined and cannot be modified. Am I understanding this correctly?

  • 0 in reply to Peter Peter
    TI__Genius 9122 points

    Hi, 

    I will reply to you tomorrow.

    Regards,

    Helic

  • 0 in reply to Peter Peter
    TI__Genius 9122 points

    Hi, 

    Peter Peter said:
    custom BSL manual

    Do you have a document link?

    Maybe you can refer to main memory BSL: https://www.ti.com/lit/an/slaa600e/slaa600e.pdf

    Peter Peter said:
    how are the protection function address and the JTAG lock managed?

    Not sure what is protection function.

    For  JTAG lock, please refer to user guide: 1.11.2 JTAG Lock Mechanism Using the Electronic Fuse

    Peter Peter said:
    Specifically, are the addresses and checks, such as verifying if the BSL signature is at a specific address, as well as the JTAG lock and protection function address stored at specific memory locations, all handled by the boot code?

    For more customer BSL information, please refer to this page: https://www.ti.com/tool/MSPBSL

    main flash BSL section.

    Peter Peter said:
    This boot code is also responsible for loading the settings of the DCO, correct? The boot code itself is not the low-level assembly code that stores the signature, handles the protection functions, or jumps to the main boot function, right? Furthermore, this boot code cannot be modified because it is not visible, is that correct?

    I think yes, you can check the code in this page: https://www.ti.com/tool/MSPBSL#downloads

    Peter Peter said:
    Furthermore, this boot code cannot be modified because it is not visible, is that correct?

    If you mean the bootcode that I mentioned earlier that is invisible to the user, this cannot be changed.

    Regards,

    Helic

**Attention** This is a public forum