Current theory - This is a read fuck-up... but not one I have seen beofre?
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Do they appear in different places from run to run, or are they always in the same locations? Do you have the original binary / are they definitely not intentional / "supposed to be there"?
-
Also, is it always 8 of 64 bytes that are 0xFF? and repeated throughout?
- Još 6 drugih odgovora
Novi razgovor -
-
-
Is that just a data segment? It doesn't look like thumb code, do the 0xffs repeat across the extract?
-
All the way across.
- Još 4 druga odgovora
Novi razgovor -
-
-
Dodgy interface or cables ?
-
nah - it's way too regular an 'error' for that :-/
- Još 6 drugih odgovora
Novi razgovor -
-
-
I'd start with GND issues, next double check the power supply and make sure it's sufficient, next maybe lower the speed, and lastly throw a logic analyzer on it and check the commands it's using because the 0xff blocks seem to be consistently spaced.
-
No matter which cmds I send I get the same output from these blocks no matter where they are requested... Even at very slow speeds and as close to manual as I can with OpenOCD. No ground issues, minimal noise, and the same setup pulls firmware fine at full speed from test rig
- Još 2 druga odgovora
Novi razgovor -
-
-
Ive only seen this once and it was a ground issue
-
Also to not, i had alot more FF’s that what you have there
- Još 3 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.