-
Notifications
You must be signed in to change notification settings - Fork 335
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
loading large file needs long time #1189
Comments
@likun2, thank you for reporting the issue. While Moreover, JTAG is quite slow. 40MB in 5 minutes is about 1118481 bits per second which requires at least 1118 kHz TCK clock (and this is the lower limit since there are various overheads in the process). What is the JTAG speed you are using? In general, to further investigate the issue, I'd like to ask you to attach
|
@en-sc ,thank you for responding. |
The idea is -- the delay is increased after E.g. running on Spike with
The next time an increased delay is used (
Once the delay reaches 7 -- it becomes enough and
From this point on the delay of 7 Run-Test-Idle cycles is used. So no, loading larger files does not result in longer delays. To reiterate: I will not be able to help you without the logs. |
The load command log is as follow
cfg2 is
|
@likun2, you've cut out the part where the delay grows. Before the cut the delay is zero:
After the cut it is already huge (445):
My assumption is: maybe there is some memory that takes longer to access that is written in the cut-out part of the log? If the data you are loading is sensitive please consider loading a bunch of zeroes instead:
@likun2 please attach the part of the log where the delay increases. |
@TommyMurphyTM1234 thank you for responding. |
I have a 40MB elf file that takes about 5 minutes to load into the board using openocd and gdb. The reason why it took so long is because there is a delay function in the abstract_cmd_batch_check_and_clear_cmderr function, which is increase_ac_busy_delay.
How can we eliminate the impact of this delay function
@en-sc
The text was updated successfully, but these errors were encountered: