conanandai100

Members
  • Content Count

    12
  • Joined

  • Last visited

Everything posted by conanandai100

  1. Hi @jpeyron Yes, I pay attention to the jumpers when programming and reboot. MIO5 is set correctly according to the guide: https://reference.digilentinc.com/learn/programmable-logic/tutorials/zedboard-programming-guide/start Besides generating a new boot.bin file, I even tried to delete the whole sdk folder, modify the LED output value, regenerate/export hardware and launch the sdk again to create a new sdk project with new boot.bin file and elf. It simply showed the old content that I can tell from the LED. Just wonder if this scenario occurs before to others and any possible solution or tips that I can fix it. I tried to google it, unfortunately there is no positive information yet. Thanks, Conan
  2. Hi @jpeyron Thanks for the answer. It partly solved my problem. Yes, the flash programming works, but only for the first time. Then no matter what I reprogram, it shows the content of the original one. I wonder if there is any write protection or one-time-program mechanism as some flash memories do. Thanks, Conan
  3. Hi, Quick question about the SPI flash programming on Zedboard: when I tried to program the bin file in the hardware manager of vivado (I need to store the bitstream offline for some reasons), it requires FSBL file, while I was only using the FPGA part without anything related to SDK. In that case, shall I create a hello world project in SDK to generate the FSBL? It just doesn't make much sense to me. Thanks.
  4. Hi @jpeyron Thank you for the reply. I thought I used the WiFi variant client/server code in the TCPEchoServer/TCPEchoClient folder under the Diligent WiFi github. Do I make a mistake by copying the wrong one? I just cannot tell the difference between the wired variant and WiFi version from the code/readme file. Yes, I still have the issue unsolved. Since I replied the other post, this post can be closed. Sorry for the multiple posts as I didn't get the reply of the other at that moment. Best, Conanandai
  5. Hi @JColvin Thank you so much for your reply! I am not sure if there is any difference for the wired TCP server and WiFi in the code that I didn't notice, cause the readme file of Pmod WiFi github doesn't mention it, and I actually didn't find any code related to the wired TCP setup. I just copied the main.cc file from the TCPEchoServer folder to my project (the server Zedboard), and same to the TCPEchoClient main.cc file to other SDK project on the other Desktop, which is connected to the client Zedboard. Changed the IP address, ssid and passphrase to the same thing. Maybe I missed something I was not aware of? As I wrote in another post later (sorry for the confusion and multiple posts), if I enable my Desktop WPA2 with the same ssid and password, both server and client on the Zedboard were able to connect the Desktop. So I guess I am using the correct code, and the Pmod WiFi is working to some extent. But those two FPGAs cannot find each other. I just wonder what is missing. I will check the IP status definition in the deIP.h file and MRF24 datasheet. Thanks again for pointing it out. Best regards, Conanandai
  6. Hi I am having trouble to setup the Zedboard Pmod WiFi communication. I used the TCP server and client demo, but two zedboards couldn't find each other. If I enable my Desktop WPA2, both server and client were able to find it. I wonder there is anything not mentioned in the github instruction. Additionally, once I tried to switch WPA2 to WEP40 or WEP140, there are errors while building the project in SDK: 'keySet' was not declared in this scope 'WEP40KEY' in 'class DEWFcK' does not name a type But keyset has been defined in the header. Any advice? Thanks.
  7. Hi, I am currently running the Pmod WiFi TCP demo on two zedboards and encounter an issue as below: For the server, it gave me a status 0x10003A00. For the client, it gave me a status 26845304. Unfortunately I cannot figure out the definition of the IPstatus in the demo. I checked my vivado project and zedboard setup, which seemed to be correct. I am using USE_WPA2_KEY with the same ipv4 address, ssid, and password btw. Is there any hint for debugging based on the current information? Thanks in advance.
  8. Hi @jpeyron That's very helpful! Thank you again for your kind advice. Best, Conan
  9. Hi @jpeyron, Thank you for your quick reply. That's a pity. May I follow up with one more question? How about using PmodBT2? Does it support peer-to-peer communication between multiple Zedboard? I read the guide "How to Auto-Connect 2 PmodBT2's Together" quickly but failed to find the answer. Appreciate your help! Best, Conan
  10. Hello, I am new to Zedboard and trying to establish ad-hoc connection between several Zedboards using the digilent Pmod WiFi antenna. The Pmod WiFi video and github code are pretty helpful, but I am not clear for the SDK side, specially for the way to enable the ad-hoc function. Does it include in the Pmod WiFi code already? Or is there any existing code that I can refer to? Thanks a lot!
  11. Hi @jpeyron, Thank you for your reply. Honestly I am new for zynq board. I am trying to get started from Microblaze that I am more familiar with and easy to follow with the wifi demo. Since Zynq processor includes the DDR3 SDRAM controller already, that is much more straightforward. I will remove the mig core then. Thanks again for the advice! Best, Conan
  12. Hi, I am trying to build a wifi communication between Zedboard and Raspberry Pi. I referred to this link: https://www.youtube.com/watch?time_continue=8&v=KTeTMv3oiPw. At the very beginning, I encountered an issue when building customize the MIG core. The target is set to digilent Zedboard (xc7z020clg484-1). I have added the board library. There is no memory selection under the board, so I tried to initialize the MIG by myself. Then in the constraints section, I cannot find the corresponding pins according to the schematic. I would like to know if there is any way to solve it. Thanks a lot!