Hello,
We have a custom HW equipped with Freescale i.MX35 processor and Spansion S29GL01GP NOR FLASH (1024x128kbyte sectors).
For erasing and programming the FLASH we wanted to use our J-Link Pro interface.
We could connect to the target correctly.
When we tested the sector erase time, we got reasonable results (~87s for erasing 128 sectors).
But when we wanted to program the FLASH, we experienced very low flashing speed: 474 byte/s.
We performed speed test (IRAM, 128kbyte) which reported ~181 kbyte/s down and ~188 kbyte/s up speed.
When we enabled the "Use target RAM" for IRAM and 4 KB, the RAM check timed out.
After that we changed the RAM size to 1 KB. With this setting the RAM verification passed, but the subsequent erase / program operation timed out.
Did anybody experienced such a slow flashing speed?
If yes, did anybody find the reason behind that?
The "Use target RAM" option seems to be useless.
Did anybody use it with i.MX35 target?
Best regards,
Gyula Kovacs
We have a custom HW equipped with Freescale i.MX35 processor and Spansion S29GL01GP NOR FLASH (1024x128kbyte sectors).
For erasing and programming the FLASH we wanted to use our J-Link Pro interface.
We could connect to the target correctly.
When we tested the sector erase time, we got reasonable results (~87s for erasing 128 sectors).
But when we wanted to program the FLASH, we experienced very low flashing speed: 474 byte/s.
We performed speed test (IRAM, 128kbyte) which reported ~181 kbyte/s down and ~188 kbyte/s up speed.
When we enabled the "Use target RAM" for IRAM and 4 KB, the RAM check timed out.
After that we changed the RAM size to 1 KB. With this setting the RAM verification passed, but the subsequent erase / program operation timed out.
Did anybody experienced such a slow flashing speed?
If yes, did anybody find the reason behind that?
The "Use target RAM" option seems to be useless.
Did anybody use it with i.MX35 target?
Best regards,
Gyula Kovacs