CCS/MSP432E401Y: Ehernet Bootloader in MSP432E401Y

Hi,

I sent it to a concerned engineer. We will get back to you ASAP. Please bear with us.

Thanks,

PM

Hi,

Thanks for your quick response ...Write soon!

Hello Sai,

I have gone through that link but, the user in that link was not getting the TFTP read request from the BSL But, I am at least getting the TFTP read request without a file name. 

Thanks,

Rupam

Hello Rupam,

Thanks for the clarification! That is interesting.

To summarize, the BootLoader is being invoked and BootP interaction is working as expected between the Bootloader and BSL scripter. The issue is that BSL scripter is sending incorrect TFTP packets (missing source file name). Feel free to correct if you think I missed something.

I will forward this request to the development team to see if they have a solution.

Thanks,

Sai

Hello Sai,

You summarised the issue correctly.

thanks for your quick and humble assistance.

Eagerly waiting for your reply.

:) 

Thanks,

Rupam

Rupam,

Thank you for your patience. Unfortunately, we currently do not have a solution yet, but are still looking into this issue. I will keep you posted.

BR,

Seong

Hi Seong

Glad to hear that you are still looking into this issue,  Waiting for your solution .

Thanks and Regards 

Rupam 

Rupam,

Yes, I apologize for the delay. Frankly, it may possibly take another week or two before we can share any solution. In the meantime, consider using the LM-Flasher tool as an alternative until we have better clarity on this issue.

I will let you know once I hear back from the subject matter expert who is currently troubleshooting this.

BR,

Seong

My first thought is that some (other) DHCP server on the network has responded to the BOOTP request. Since it didn't know about this BOOTP client, it reported a null filename and a Server Address of 0.0.0.0 in its response. (The BSL uses these items without much scrutiny.)

It would be very interesting to see the immediately preceding Wireshark trace items. It seems possible that BSL-Scripter never even saw that packet (given the destination address), and was reporting a Timeout instead.

Is there some way you can disconnect your PC and Launchpad from the rest of your network?

Hi Seong,

Thanks for your feedback.

Rupam

Hello Bruce,

Do you want me to connect the launchpad and PC using single LAN cable ...excluding the rest of the network???

Rupam

Hi Seong 

Could you please send me any reference to use the LM flash programmer with MSP432E401Y.

Yes, that's the experiment I'm suggesting. It needn't be a single cable -- if you're using a switch just disconnect that from the rest of your network. 

My hypothesis is that there's some DHCP server on your network (you probably don't even know where it is) that is configured to respond to BOOTP requests. Since it doesn't know about your device, it doesn't know what TFTP server/file to give you so it gives you nulls for those. (Some would argue that that server is mis-configured, but I think that behavior is (just barely) within RFC 1534.) The BSL relies on BSL-Scripter (or suitable substitute) being the only BOOTP/TFTP that responds to it.

I do most of my experiments on a private network containing only a laptop, a router, and my target. This avoids interference from the corporate network (and also keeps the IT people from yelling at me).

Do you by chance still have the Wireshark trace you put in the Original Post? I think the items immediately preceding the item you showed would be enlightening.

Rupam,

Thank you for your patience. Please bear with us as we try to provide feedback by the end of this week at the latest. 

BR,

Seong

Rupam,

We apologize for the constant delay. We've needed additional time to setup the visual studio project for the TFTP debugging. The USB library used was not linked correctly.

We will try to provide a solution/work-around by the end of this week.

Thanks,

Seong

Hi Rupam,

Were you able to resolved your issue?

Thanks,

Riz