Skip to content

README.md: Adds instructions how to obtain bootloader-details #73

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

Merged
merged 1 commit into from
Dec 20, 2019
Merged

README.md: Adds instructions how to obtain bootloader-details #73

merged 1 commit into from
Dec 20, 2019

Conversation

VeijoPesonen
Copy link
Contributor

@iot-pdmc
Copy link
Collaborator

Thanks for your changes.
@ARMmbed/pdmc-integrators please review.

@VeijoPesonen
Copy link
Contributor Author

VeijoPesonen commented Dec 16, 2019

@wajahat-ublox for your information.

Copy link

@MarceloSalazar MarceloSalazar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not keen on adding a way to reverse-engineer information on the memory map.
Instead is best to point developers to the corresponding json file that will contain the information.
Usually, both the bootloader and application configuration are created at the same time.

@VeijoPesonen
Copy link
Contributor Author

Instead is best to point developers to the corresponding json file that will contain the information.

I can't find the same information from the corresponding json file

@teetak01
Copy link
Contributor

This is the manual way of generating the hash. Alternatively you can find the information as part of bootloader releases https://github.com/ARMmbed/mbed-bootloader/releases/tag/v4.1.1

There is a text-file which contain this information.

@MarceloSalazar
Copy link

MarceloSalazar commented Dec 16, 2019

Are you saying this is a kind of random value that's generated at compile time?
It would be great to understand the logic behinds this.

@wajahat-abbas
Copy link
Member

wajahat-abbas commented Dec 17, 2019

Are you saying this is a kind of random value that's generated at compile time?
It would be great to understand the logic behinds this.

If i am not wrong, this is the address where bootloader lies. It is was earlier printed on serial but was later removed to reduce memory footprint. Now the only way is by reading it from .map file of the image.

More information on linked issue.

@VeijoPesonen
Copy link
Contributor Author

Are you saying this is a kind of random value that's generated at compile time?
It would be great to understand the logic behinds this.

Please see the bootloader documentation about the subject

@MarceloSalazar
Copy link

@VeijoPesonen thanks for the link to the docs. It looks we're still referring to information generated on the serial port.
I'm ok to leave the comments on the docs on how to find out the hash info. In the future, I'll be looking at generating this automatically after the compile/link process.

@teetak01
Copy link
Contributor

@MarceloSalazar that would most likely be a feature request for Mbed CLI to provide such functionality.

Copy link

@MarceloSalazar MarceloSalazar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good as it's now

@teetak01
Copy link
Contributor

@VeijoPesonen can you rebase this?

@VeijoPesonen
Copy link
Contributor Author

Rebased.

@teetak01 teetak01 merged commit df9375b into ARMmbed:master Dec 20, 2019
@VeijoPesonen VeijoPesonen deleted the readme_bootloader-details branch December 20, 2019 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Getting value of "update-client.bootloader-details"
5 participants