My program is getting stuck at a part in the disassembly labeled _primIO when I run it for no obvious reason. It looks about the time that I am writing a file out.. Could someone shed some light on why it may do that?
primIO is the default IO device used to perform IO functions - this works via the JTAG to perform any IO operations via the PC (be it printing to the console, or performing file operations on the PC). During heavy IO (like reading/writing a lot of data from/to a file), we would expect the processor to loop through the primIO code many times to complete the operation.
If your application is in this section of disassembly, it will be because the application is performing IO operations. You say that it gets 'stuck' - does the processor automatically halt here? Are you unable to step through the code (either in the disassembly window or the source window)?
Are you running the application on hardware, or in the simulator?
I am running in debug agent mode (hardware). The processor doesn't halt, it just keeps running at that point until I manually halt the program. The odd thing is that it doesn't look like any data is being written to the .txt file because the size of the file is still at 1 KB.
we do expect file IO to be slow via the USB Debug Agent - how long have you left it running without seeing any increase in the file size beyond 1Kb? How much file IO are you performing - how big are you expecting the file to become?
When you halt and try stepping through the disassembly window, is the PC stuck at a certain instruction, or does it appear to loop through ok?
When you load your project, please ensure that the "primIO" breakpoint is enabled under 'Settings'->'Breakpoints'. This automatic breakpoint is required for primIO functionality.
We will likely need to look at example code to reproduce this issue. If you wish, you can post it here. If you prefer, you can contact us through private support via the link below:
Retrieving data ...