Skip to content
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

Issue with DFU prog on F767 #11

Closed
rusefillc opened this issue Dec 6, 2021 · 6 comments
Closed

Issue with DFU prog on F767 #11

rusefillc opened this issue Dec 6, 2021 · 6 comments
Assignees
Labels
bug Something isn't working internal bug tracker Issue confirmed and reported into a ticket in the internal bug tracking system

Comments

@rusefillc
Copy link

rusefillc commented Dec 6, 2021

It looks like stm32cube programmer does not erase proper page 12/erases non existent page 8 in some corner case of dual bank

I'm having a problem with STM32CubeProgrammer and a 1MB STM32F767ZG configured in dual bank mode. On the left, I tried to flash a 520k bin to the device, over the top of previous firmware.

Expected behavior: erase sectors 0-7, 12, then write 520K bytes starting at address 0x08000000.

Actual behavior: erases sectors 0-8, then write 520K bytes starting at address 0x08000000.

Since it tries to erase the non-existent sector 8, sector 12 (the actual sector at 0x08080000) doesn't get erased and as such the contents of sector 12 get corrupted by the multiple writes without an erase.

See screenshot below: stm32cubeprogrammer tries to erase sector 8 at 0x0808 0000, but in dual bank mode, there is no sector 8!

image

See https://community.st.com/s/question/0D53W00001EEBXXSA5/stm32cubeprogrammer-incorrectly-erases-on-dual-bank-1mb-stm32f7

@PierreLeCorre
Copy link
Contributor

Dear @rusefillc , thanks to transmit this information. Unfortunately, this issue is not related to the content of this repository and so i closed it.

For your information, i have also transmitted your issue to our development team with the internal reference 120183.

@rusefillc
Copy link
Author

@PierreLeCorre is there a more relevant github repo for this issue? What's the best way to check on internal ticket 120183 going forward?

@PierreLeCorre
Copy link
Contributor

@rusefillc We don't provide access to our internal bug tracking system and we don't provide GitHub repository for the STM32CubeProgrammer where you can submit issues. Then, you have taken the correct path to submit your issue on https://community.st.com.

@rusefillc
Copy link
Author

@PierreLeCorre this did not make into 2.10 update recently, do you know if there is hope for 2.11?

@rusefillc
Copy link
Author

fresh screenshot of 2.12

image

@rusefillc rusefillc changed the title Issue with dfu prog on F767 Issue with DFU prog on F767 Jan 30, 2023
@ALABSTM ALABSTM added bug Something isn't working internal bug tracker Issue confirmed and reported into a ticket in the internal bug tracking system labels Aug 11, 2023
@ALABSTM ALABSTM added this to To do in stm32cube-mcu-fw-dashboard via automation Aug 11, 2023
@ALABSTM
Copy link
Contributor

ALABSTM commented Aug 11, 2023

ST Internal Reference: 120183

@ALABSTM ALABSTM moved this from To do to Done in stm32cube-mcu-fw-dashboard Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internal bug tracker Issue confirmed and reported into a ticket in the internal bug tracking system
Projects
Development

No branches or pull requests

3 participants