- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software: Code Composer Studio
Hello everyone.
My problem is about to MSP430FR6047 BSL.
While I am using MSP430FR6989 (BSL version : 00.07.34.B2), I achived download to MCU with BSL.
All functions of BSL (Mass erasing, reset with BSL etc.) were experienced by me. I didn't encounter any problem at MSP430FR6989 BSL core.
But, with MSP430FR6047 (BSL version : 00.08.35.B3) , I encounter two unusual behavior;
First; MSP430FR6047 does not response to UART after mass erasing operation.
Second; Loading PC to @4400 or @4000 is not cause a reset. (I can reset by writing 4400 to PC with BSL at FR6989)
What is the problem? Is there any difference between two BSL version?
Hello Mesut,
we're looking into your problem, and will come back to you later today. Have you check on our BSL landing page about the documentation on our main BSL landing page? There you should be able to find the documents describing the BSL details and potential differences between different families and derivatives.
and FRAM device BSL User's Guide.
Best regards
Peter
I resolved BSL-stricpter's "header incorrect" problem writing PARITY to MODE line in script input file.
But result is same. BSL is not responsive to any command after mass erasing performed.
Hello Mesut,
we have once again tried to reproduce, what you're experiencing on your side, and have performed with an MSP430FR6047 a mass erase using the BSL rocket and a target board for the MSP. We were able to execute the mass erase and also to communicate after the mass erase with the MSP using BSL.
This means, we do not see the issues you're observing. So basically all indicators are pointing so far to your setup, as root cause of the failures. Thus we need to understand perfectly your setup and the actions you're applying.
We though would recommend first getting the BSL communication and flow with a tested environment, means using an official HW tool and SW (BSL scripter) to eliminate at least some of the unknown variables.
Please find here also an outline flow, of what we understood from your descriptions, what should be happening on your side.
1. step is the mentioned SW invoke of the BSL you mentioned. If this is successful, the device will be waiting on the password from the host.
2. Then the host transmits the password and the target MSP should acknowledge this. This seems to be working on your side.
3. Then the host transmits the mass erase command to the target MSP. In this case the target device should only execute the mass erase, but not send a response. Also this steps seems to be working on your side, at least to the extent, that the target MSP is executing the mass erase.
4. In our case with our tool chain and setup, after mass erase, the target device would remain in BSL mode, means does not require a HW or SW invoke of the BSL, but waits again for the BSL password. Keep in mind now the PW has changed due to the mass erase. According to your explanations, this step does not work anymore on your side.
Thus as explained above, we're recommending to eliminate as many differences between your and our setup, to reach a functional setup, and then start adding the necessary modification towards your desired setup, one modification only in each step and test, whether it still works. But the goal should be definitely starting with a setup that works.
If you can provide us more detailed information on your setup we might in addition try to identify some critical details, which might be contributing to the observed problem.
Best regards
Peter
**Attention** This is a public forum
