Please check if the data is seen on the scope as expected.Ģ) Once the step 1 works, then I would suggest you to try to debug the initial communication between the DSP and the PC as mentioned in the code below step by step: Regarding debugging the DSP's communication with the GUI running on the PC is concerned, I have following suggestions:ġ) With the existing connections and using any other simple RS-232 communication software, I would suggest you to transmit a single byte from the PC and probe the corresponding DPI pin on the DSP end. I shall try to correct this in the next update of the application note. I agree that the current code shows some warnings at the build time because of bad programming practices.Sincere apologies. The dsp ICE shows the code is waiting for UART rx and not getting any.ĭoes the GUI run correctly on Windows 7 64 bit? dll files in the GUI directory have been copied to c:\windows\system32. The GUI never unfreezes and it has to be killed from Task Manager. This is on a PC running Windows 7 64 bit. When I run the code and start the GUI, then issue an Upgrade command, the GUI freezes and the title bar adds "not responding". I removed the wait-for-button part of the code as my board does not have a button and I want to always enter the flash uploader for testing. If '_load_application' is defined in a different file, use ".extern". Use '_load_application.end' or '_load_application.END' to mark
".\boot_kernel.asm":28 _load_application: The ending boundary of the function for debugging information forĪutomated statistical profiling of assembly functions.Īssembler totals: 0 error(s) and 1 warning(s) Use '_lib_RSTI.end' or '_lib_RSTI.END' to mark g assembly with global function without ending label. Configuration: 21469_SSL_Parallel_FLASH - Debug. I can build the code in the 21469_SSL_Parallel_FLASH.dpj project, and get these warnings: I don't have the 21469 ez-kit lite but have a design using the same flash and serial port design as that board.
0 kommentar(er)
