• Content Count

  • Joined

  • Last visited

About hearos

  • Rank

Recent Profile Visitors

133 profile views
  1. I have not had any activity listed when trying the "dmesg" so I went to buy a new cable, and that actually was it. Thank you for the hint!
  2. I use a Nexys 4 DDR board for some time now. I never used to have problems when programming the device. Today I tried to program the device as I did many times before, but it didn't work. It said I should check whether I connected the board properly and so on. So I checked the Jumper settings and everything. Now I tried to see whether the FTDI FT2232HQ chip is recognized. When using the bash command "lsusb" the chip is not listed anymore. Does anyone know what the problem could be? How else could I check whether the FTDI FT2232HQ chip is working or not? I need to finish a report and therefore I need the device working as soon as possible, thank you for your help.
  3. @jpeyron Dear Jon I found that the ultimate problem was the mix of C and Cpp (the Pmod SD lib contains cpp files). The Block Design was configured correctly in Vivado, only the Make process didn't work properly. Using the Extern C commands (as you did explicitly mention in your post and implement in the project above) solves the problem. So to use the freeRtos I added additional AXI timer and Interrupt Controller. Now there is a problem this way, it does only work when the main is a cpp-file (.cc). When one uses the FreeRtos OS Plattform configuration, the main will be a c-file (freertos_hello_world.c). When the main is renamed to freertos_hello_world.cc the message below occurs when trying to run the project. So again a problem in the Make process. What would you suggest to do to solve the issue? Best regards Harris Message: **** Build of configuration Debug for project SD_Card_Rtos **** Nothing to build for project SD_Card_Rtos
  4. Hi @jpeyron Thank you for the verified Project you posted above. SD card works now. I just had to adapt the paths (board files, and Pmod files) in the xilinx project file. I still get the same warnings but they can be ignored. Seems like the SD card itself was not the problem, maybe the problem was with the memory (not enough space to store the program) or with the cache (in case the SD card needs these to work properly). I will make further investigations on the issue. Nevertheless, thank you, with your help I got it working for the purpose I need it. Best regards Harris
  5. @jpeyron Hi Jon Do you have news regarding the SD card project? Best Regards Harris
  6. @jpeyron That sounds great, thank you Jon!
  7. @jpeyron I use the SD card (onboard), uartlite, timer and interrupt controller (so that I can run freeRtos later). I use the newest IP library (hotfix OLEDrgb). I use Vivado 2018.3 with a Nexys 4 DDR. As mentioned above, with given configuration (without any additional xdc file nor changing anything else) I get the warnings (for pins 7 to 10): [Common 17-69] Command failed: BOARD_PART_PIN cannot be assigned to more than one port ["/home/harris/EmbSys/nexys4/SDcard/SDcard.srcs/sources_1/bd/design_1/ip/design_1_PmodSD_0_0/design_1_PmodSD_0_0_board.xdc":7]
  8. I am still stuck at this problem. I got most of the modules (OLED, Encoder, KYPD, SRAM) I need working but the SD card. I tried both onboard and external, neither of them seems to work. Yet I need to be able to store larger amounts of data, bitmaps and sounds and so on. Can anyone help?
  9. @jpeyron if I ignore the critical warnings and generate the project and start SDK I will have problems making the board support package. See the screenshots below. Interestingly the KYPD also has a wrong board setting as the SD IP (arty instead of nexys-a7-100t) but it will work in SDK. Thank you for your help.
  10. Thank you @jpeyron for your answer. I tried using the on board SD and the external, none of them were working. In the following set up I use a PmodOLEDrgb and a PmodSD (onboard config) IP block. The OLED IP works fine, when I add the SD IP, problems occur. I validate te design: Following warnings appear: When I press generate Bitstream following critical warnings appear: I use the hotfix-PmodOLED_RGB library: When I go check the files, for the working OLED and the not working SD I see that in the SD files the wrong board (arty instead of nexys-a7-100t) is set: So can I just change the lines in the files to make it work? Is it a problem in the hotfix library that Digilent needs to solve? Thank you for your help!
  11. I'm trying to run the PMOD SD IP core on a Nexys 4 DDR, using simple drag and drop from the board tap. I also add a microblaze and an UARTlite for communication. I wish to run the SDK (autogenerated) example of the SD PMOD IP core. I have used the same approach with the OLED and several other PMOD and it worked out fine. But with the SD card it fails, I get these critical warnings. I am surprised there is a problem at all, since I only used the PmodSD IP core, written by Digilent. See below. The file of concern below: Thanks for any help!