Handling 24 GHz_pynq_designs Files and Resolving Errors

[Gloria-Gly]

I hope this message finds you well.

I am currently learning about 24GHz_pynq_designs and am trying to understand the correct usage sequence for the provided folder. The readme file is quite brief, and I am unsure if there are additional steps I should follow..

At present, I am attempting to run the aerpawAPI file. Following the error prompts, I have placed the bitstream file you provided into the created folder. However, I am still encountering an error. The error code I am seeing is: raw write() returned invalid length 5636 (should have been between 0 and 33).

Could you please provide any guidance or tips on how to resolve this issue?

Thank you very much for your assistance.

[alphansahin]

Hello! Unfortunately, there is no detailed documentation at this time. Maybe you need to provide further information on how you are the commands. Just so you know, the current design only supports RFSoC2x2. The bitstream file name should be as follows:

    fsysref = 32
    fpl = 192
    frfdc = 1536
    decimation = 1
    tagBitStream = 'v47'

    self.bitStreamAERPAW = 'aerpawFPGA_' + str(fsysref) \
                                         + '_' + str(fpl) \
                                         + '_' + str(frfdc) \
                                         + '_D' + str(decimation) \
                                         + '_' + tagBitStream + '.bit'

You may take a look at input arguments for the API commands in aerpawAPI.py. For example,

    if clientMsgParsed[0] == "setupReception":
        if len(clientMsgParsed) == 3:
            modeRX = int(clientMsgParsed[1])
            numIQdataSamplesPerTransfer = int(clientMsgParsed[2])
            success, status = self.fgpaControllerObj.setup_reception(modeRX, numIQdataSamplesPerTransfer, isRawFormat=True)
            if success == True:
                responseToCMD = successMessage 
            else:
                responseToCMD = status                    
        else:
            responseToCMD = invalidNumberOfArgumentsMessage

This command requires two arguments where the first argument is "mode" as an integer, and the second argument is the "number of IQ data samples for each transfer", again as an integer.

[Gloria-Gly]

Thank you very much for your kind reply!

Here's what I did in detail: I copied the entire design_pynq_28GHz folder to my pynq board as per your instructions inside READ ME. My board is a RFSoC4x2 though. I chose to run the file aerpawJupter.ipynb first, and while doing so I realized that I was missing the bitstream file, and I found the appropriate bitstream file in your design_FPGA folder. I copied the .bit and .hwh together to the current folder and modified the program to make the names of the program and the files match and then re-ran the program. Then I got the above error: raw write() returned invalid length 5636 (should have been between 0 and 33). I skipped this line and ran the following EVK controller related program and it ran without any problems.

Without more detailed instructions on how to use it, I have the following new questions:

1. I found your cmdList in the folder, and I was wondering when this is required to enter these commands?
2. Is my first step from aerpawJupter.ipynb correct, if so what is the next step to configure, if not which file should I start with to configure my board? I observed that there are some files WifiSTartup and so on that are not in the folder 28GHz, but I observed its application in the cmdList file, so I found it inside the 60GHz folder and copied it, and I want to know how they are going to be used? Because I didn't find his relevant calls in the main program aerpawJupter.ipynb.
3. I want to get the data output image like you show in test_v0, these MATLAB codes I need to run on the computer and not on the PYNQ board right? And what is the order of running the MATLAB and python code?

Thanks for your time and your kind response again!

[alphansahin]

Okay, now I understand it better. The main issue is that you use RFSoC4x2, which is not supported by these files. RFSoC4x2 has a different clock network. You need to reconfigure almost everything, including the pins, processor, etc. Without this, it will not work at all. The second issue is that aerpawJupter.ipynb is really not for the actual design. I was using it merely for debugging. Hence, I don't recommend using it as a central file.

1. CMDlist is simply copying and pasting some commonly used commands to the prompt window.
2. Please don't use aerpawJupter.ipynb. I recommend starting the API and interacting with the API through a host computer over TCP/IP.
3. You can use any host computer you like as long as you can generate TCP commands. It can be MATLAB or Python (or any language)