- #Procomm plus windows 7 64 bit .dll
- #Procomm plus windows 7 64 bit serial
- #Procomm plus windows 7 64 bit update
- #Procomm plus windows 7 64 bit upgrade
- #Procomm plus windows 7 64 bit code
Printf("Copy the ldr file data to memory.\n") Printf("Unable to allocate memory.\nProgram terminated.\n") If((pData=(unsigned char *)malloc((length+1)*sizeof(*pData)))=0) Printf("Allocate memory to load the ldr file data.\n")
Printf("Length in bytes = %d.\n",length) Printf("Length is 0, nothing to upload.\nProgram terminated.\n") * (count the number of x's in the file) */ Printf("Determine the length in bytes of the ldr file.\n") Printf("Unable to open file.\nProgram terminated.\n") Printf("Using COM port %d.\n",comport+1) Printf("\nProgram to upload the contents of upload.ldr to the adsp-21469 flash.\n")
#Procomm plus windows 7 64 bit code
Build and execute the code in a cygwin bash shell, it appears to work. There are lots of printf's to confirm the uploader execution is progressing. The c code for the uploader is in the attachment and repeated below. Using the rs232 library found here: I wrote a text mode uploader to bypass the possibly broken GUI version. Once these steps work okay, then it means that the problem is with the GUI only and not with the DSP-PC interface.ģ) If it indeed turns out to a problem with the GUI, I can provide the VC++ source code of the GUI. Check if the DSP receives this byte correctly and so on.As you see, these debugging steps are independent of the GUI. Then from the PC end, send a byte LENGTH_ACK(0x03) to the DSP. If yes, you can run the DSP code further by putting a breakpoint at "Write_UART(LENGTH_ACK) ". Check if this byte is correctly received by the PC. with the help of a breakpoint, you can first run only the code on the DSP which sends the byte START_LOADING(0x01). Read the most signnificant byte of 'offset'Į.g. Read the third least signnificant byte of 'offset' Read the second least signnificant byte of 'offset' Read the first least signnificant byte of 'offset' Read the most signnificant byte of 'length' Read the third least signnificant byte of 'length' Read the second least signnificant byte of 'length' Read the first least significant byte of 'length' Signal the host that the slave is ready to communicate 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.
#Procomm plus windows 7 64 bit update
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?
#Procomm plus windows 7 64 bit .dll
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.
#Procomm plus windows 7 64 bit upgrade
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:
#Procomm plus windows 7 64 bit serial
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)
