-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question on devices #1
Comments
Hi Bob, Thank you and best regards, |
Hi, Max,
will do.
bob s.
On Nov 18, 2021, at 2:49 AM, Max Gröning ***@***.******@***.***>> wrote:
Hi Bob,
I'm glad the project might be of use for you - even though my project is in an initial state.
You are more than welcome to provide feedback, sources (when you are done), pull requests.
Thank you and best regards,
Max
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMS2KEL4ANRBLJK6YFMPNPDUMSVYBANCNFSM5IFAYB3A>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hi, Max,
I’m at the point where everything (the data, the crc) is perfect but the boot fails.
I’d like to read back the flash’ed data block in case the problem is the timing on the flash write on the 432 side.
I see you haven’t implemented ebh_tx_data_block_32(), so I am going to try to code that.
I’ve got a question.
ebh_format_package() sends data for rx, do I just replace the send with a receive for tx?
thanks,
bob s.
On Nov 18, 2021, at 2:49 AM, Max Gröning ***@***.******@***.***>> wrote:
Hi Bob,
I'm glad the project might be of use for you - even though my project is in an initial state.
You are more than welcome to provide feedback, sources (when you are done), pull requests.
Thank you and best regards,
Max
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMS2KEL4ANRBLJK6YFMPNPDUMSVYBANCNFSM5IFAYB3A>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
FYI
Begin forwarded message:
From: TI E2E support forums ***@***.******@***.***>>
Subject: [Arm-based microcontrollers forum] MSP-EXP432P4111: might have found 2 bugs in BSL, version MSP432BSL_1_01_00_00
Date: December 2, 2021 at 9:11:07 AM EST
To: robert schaefer ***@***.******@***.***>>
[http://www.ti.com/content/dam/tinews/images/blogs/category/company/wwe/spacer.gif]
A Message from the TI E2E™ design support forums
[http://www.ti.com/content/dam/tinews/images/blogs/category/company/wwe/spacer.gif]
[Texas Instruments]
<https://e2e.ti.com/members/4676013>
***@***.***
robert schaefer<https://e2e.ti.com/members/4676013>
Part Number: MSP-EXP432P4111<https://www.ti.com/tool/MSP-EXP432P4111>
Hi,
I needed to creat a bespoke version of the ubuntu scripter that talked to the BSL on a bespoke board because of error messages that had no detail.
I am working with a launchpad first because the lab setup makes it difficult to develop new software or bring the bespoke board back home.
I assume the launchpad is using MSP432BSL_1_01_00_00, correct me if I am wrong.
Problems:
1. the version per the BSL source is 2 bytes, but the documentation and the handler for the version return 10 bytes.
the reason that I believe this is a bug, is the variable that holds the version is declared as a 2 byte array:
BSL432_Command_Interpreter.c: const uint8_t BSL432_VersionVendor[2] = {0x00, 0x00}; // TI production build uses
case BSL432_TX_BSL_VERSION:
{
BSL432_CI_sendDataBlock((uint32_t)(&BSL432_VersionVendor), 10);
break;
}
This might be a double-bug in that this is the version vendor and not the version id, which is also a 2 byte variable
also, when 10 bytes are returned, they seem to be sending the contents of the next variables declared.
2. my attempts to flash load on the launchpad return no error, but the launchpad does not boot to the program loaded,
I print to console the byte blocks and this matches the .txt file loaded.
I am guessing at this point the flash might not have loaded, perhaps due to timing between commands.
So I am attempting to code the read flash function to read back and compare, i.e. BSL432_TX_DATA_BLOCK
On requesting a 256 byte block, the BSL attempts to send 256+1 bytes, the extra byte is not the crc, but seems to be an off-by-one error
in the function: BSL432_CI_sendDataBlock statement: BSL432_PI_sendData(bytes + 1);
thank you for your consideration.
bob s.
View online<https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1058839/msp-exp432p4111-might-have-found-2-bugs-in-bsl-version-msp432bsl_1_01_00_00>
You received this email because you have this notification enabled in your user settings. To stop receiving notifications update your user settings<https://e2e.ti.com/user/settings> page.
Flag<https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1058839/msp-exp432p4111-might-have-found-2-bugs-in-bsl-version-msp432bsl_1_01_00_00?AbuseContentId=41da360b-01e7-4c97-b8ec-e62f38bf0136&AbuseContentTypeId=46448885-d0e6-4133-bbfb-f0cd7b0fd6f7&AbuseFlag=true> this post as spam/abuse.
[https://e2e.ti.com/notification/read?NotificationId=c27bcaed-65f7-46ec-881a-1f882941dd30]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hi,
I was working with the linux bootloader provided by TI but it was delivered in binary, is fragile, and doesn't identify detailed errors.
I am using your code as a basis for a better linux host bootloader, and I am also modifying some of your core to be less fragile and return more information on errors returned by the firmware BSL.
By fragile, I mean that sometimes a sync, if late or repeated, will be responded to by a not-a-header-ack which, to my thinking, is ok and not an error. Your initial sync code just returns w/o reporting what is going on inside, such as timeout.
Rather than identify issues one-by-one that are shades of judgement and interpretation (i.e. you might not agree),
I'm just going to hack away.
Question/issue: I am wondering if I can give you the source when I am done, to do with whatever?
bob s.
The text was updated successfully, but these errors were encountered: