STM32L476 DISCOVERY: Fails to write with large (e.g. > 64K) file size #995
Assignees
Labels
Milestone
Comments
|
Can you please also test the latest release (v1.6.1) and the current |
|
I just tried with the latest |
|
Thanks for the feedback. |
|
In |
|
Uh wait - we need to evaluate that. 👀 |
|
@geoffreymbrown: What do you think about this? |
|
I'm not sure about there being a reduction -- the change I made did
decrease the outer loop to 30, but it also increased the wait time in the
inner loop so it wasn't banging on the usb connection as frequently. The
total wait time went up. The only issue I see is that I don't have a
good understanding of the actual physical requirements. Increasing the
overall wait time shouldn't affect the successful writes -- only the time
it takes to fail. This isn't likely to be a problem.
I don't personally know what it is measuring -- I had assumed it was the
time to write a page, so I don't have a grasp on why writing large numbers
of pages is causing this problem.
…On Sun, Jun 28, 2020 at 5:36 AM nightwalker-87 ***@***.***> wrote:
@geoffreymbrown <https://github.com/geoffreymbrown>: What do you think
about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#995 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANL6UQU5IPN4UHS6WHEV4DRY4FLVANCNFSM4OFIEYQA>
.
|
|
I pulled code recently (in the last few days) from the develop branch and built it, hoping this issue would have been resolved for the STM32L476, but it still has not been: |
|
I seem to have the same problem with an STM32F767. And since I'm busy bisecting anyway:
54e5627 doesn't build because of undefined EDIT: Looking at the commits, that can't be right 😕 . Trying again. EDIT2: OK, it works every second time. Seems I've been hit by #1054 instead. |
|
Another attempt, this time with EDIT: I tried smaller images now, and they all fail. So maybe the problem is not related. |
|
Sry, but that does not seem to help any further... |
|
@Ant-ON Fixed? |
|
@Nightwalker-87 yes, it closes by #1124 |
Nightwalker-87
added
bug/fixed
status/resolved
and removed
needs/investigation
needs/testing
labels
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a repeat of a previous ticket, except with a larger file size; increasing the timeout fixed the other ticket, but it still is too short for writing the file I tried to write today, which is 96256 bytes in size. I created a new ticket because that other ticket was already closed.
st-flashFuther we kindly ask you to describe the detected problem as detailed as possible and to add debug output if available, by using the following template:
Commandline-Output:
Expected/description:
st-flashwould successfully write zeptoforth_full-0.6.0.bin to the STM32L476 MCU.The text was updated successfully, but these errors were encountered: