Thanks for your reply Peter it has been helpful. Since ez-FET on MSP-EXP430FR2433 uses SBW which is a JTAG implementation and both are locked together I have confirmed the lock just by trying to access with CSS. (And I got the message that JTAG is secured, therefore MSP-FET might be an overkill in my case, for now) Applied the lock f in-system as per the guideline-> #pragma RETAIN(JTAG_signatures) #pragma DATA_SECTION(JTAG_signatures, ".jtagsignature") const uint16_t JTAG_signatures[] = {0xAAAA, 0x0002}; I just got a BSL Rocket in my hands so today I will be playing around with the BSL as well I hope. Just one last thing which still confuses me a bit please if you can elaborate: In SLAU550S, section 3.6.1.2 shows it’s possible to change the BSL signature and password through the cmd file just as the JTAG signature as above.(perhaps only for FR235x and FR215x?). So I assume that’s not possible FR2433 since I can only find .bslsignature and .jtagsignature in its .cmd. However, the addresses for the BSL password are FFFFh to FFE0h (User defined + Vector table configuration) (The BSL password is equal to the content of Interrupt Vector table on the device as stated in the same document). Therefore if understand correctly the password and signatures/configuration is located In the top of FRAM in interrupt vectors (which range is FFFFh to FF80h) while the BSL itself is in ROM. So couldn’t one disable the FRAM Write Protection and write on these addresses in order to set a new BSL password using an in-system approach as with JTAG? It confuses me why FF80h-83h for JTAG signature and FF84 to FF87 BSL signature are accessible but BSL password is not through .cmd? Thanks a lot again, regards, Con
↧