StefanOR

Members
  • Content Count

    12
  • Joined

  • Last visited


Reputation Activity

  1. Like
    StefanOR reacted to jpeyron in GPS driver question.   
    Hi @StefanOR,
    Here is a forum thread that discusses using the GPS.ping that might be helpful for your project.  I believe that the 
    GPS_setUpdateRate(&GPS, 1000); //Sets the frequency that the PmodGPS sends sentences.
    and an interrupt is sent every 8 bytes
     GPS_intHandler(PmodGPS *InstancePtr, u32 Event, unsigned int EventData)
    sets the InstancePtr->ping = TRUE;
    The PmodGPS.c, PmodGPS.h and main.c will be the files to look through.
    thank you,
    Jon
     
     
      
  2. Like
    StefanOR reacted to jhealow in Getting Started w/ ESP32   
    Hello,
    I am trying to run AT commands on an ESP32 pmod connected to a zedboard. Both switches on the ESP32 are in the off position. My hardware block diagram is attached. When I launch SDK and open a terminal to run the AT commands, they are echoed back to me, but I don't get any other of the expected responses i.e. "OK" for the command "AT". Is my hardware configuration correct? Should I be communicating with the Pmod through an alternative to the terminal in SDK? 
    Thanks,
    Joe

  3. Like
    StefanOR reacted to jpeyron in IO standard issue when connecting USB_uart peripheral to my block design.   
    Hi @StefanOR,
    The USB UART bridge is tied directly to the ZYNQ processor.The USB UART Bridge is handled by the ZYNQ processor. When using the Digilent board files the default setting in the block automation is  configured by the board files. You do not need to  and would not be able to use the Uartlite IP Core to connect to the USB UART in this case. I have attached screen shots. The SDK code for the PmodESP32 is made to work for either ZYNQ or Microblaze designs.  
    cheers,
    Jon


  4. Like
    StefanOR reacted to jpeyron in GPS PMOD battery spec/antenna suggestion.   
    Hi @StefanOR
    Anything less than .1 in or 2.54 mm should work for the battery. I believe it is a typical coin cell size.  We have not used an additional antenna with the Pmod GPS. I would suggest to reach out to GlobalTop for their suggestion on adding an additional antenna.
    thank you,
    Jon
  5. Like
    StefanOR reacted to jpeyron in Using PMOD pins on the Zedboard as GPIO.   
    Hi @StefanOR,
    Here is a Zedboard tutorial that shows you how to use the Zedboard board files with the on-board LEDs, BTN's, and SW's. To use Pmod Pins when you add the AXI GPIO IP core you want to configure the width. Then right click on the expanded GPIO out and select the pins you would like to use. I would suggest using the T Pins instead of the I or O pins. Then when you are done with the block design and you have made a wrapper you use the pin names in the wrapper to constrain them in an XDC.   Here is the master XDC for the Zedboard. Lets say that the GPIO pins in the wrapper are named "gpio_out_t" and you want to constrain the pins to the JA Port. You would constrain the first pin like this:
    #set_property PACKAGE_PIN Y11 [get_ports { gpio_out_t[0] }]; # "JA1" 
    thank you,
    Jon
  6. Like
    StefanOR reacted to jpeyron in PMOD ESP32 Driver error in SDK.   
    Hi @StefanOR,
    In you screen shot the main.c file is not saved. After saving the main.c file does the error goes away. If not then right click on the ESP_32_joey_bsp and re-generate the board support package. If that does not fix the issue try deleting the ESP_32_joey_bsp and adding a new board support package with the exact name you used in you sdk project  "ESP_32_joey_bsp". I do not think you will need to add any additional libraries so then just select ok. Did re-adding the bsp fix the issue? If not, please attach a screen shot of your vivado block design. What version of Vivado and what FPGA development board are you using?
    thank you,
    Jon
  7. Like
    StefanOR reacted to jpeyron in PMOD ESP32 Driver error in SDK.   
    Hi @StefanOR,
    I made a project using Vivado 2018.3 for the Zedboard with the PmodESP32 on JC. I got the same error after adding the main.c to my application.  To fix this hold down the Ctrl key and left click on the xparameters.h on the top of main.c. This should open up xparameters.h. Then search xparameters.h for XPAR_PS7_UART. In my project XPAR_PS7_UART_1_DEVICE_ID was the defined parameter. So all I had to do was change XPAR_PS7_UART_0_DEVICE_ID to XPAR_PS7_UART_1_DEVICE_ID in the main.c code.  I would guess that this is a version issue with Vivado 2018.3. I have contacted our content team about this issue for the PmodESP32.
    thank you,
    Jon
  8. Like
    StefanOR got a reaction from jpeyron in PMOD ESP32 IP for use with ZedBoard.   
    Thanks so much @jpeyron
  9. Like
    StefanOR reacted to jpeyron in PMOD ESP32 IP for use with ZedBoard.   
    Hi @StefanOR,
    These critical warnings about the packaging can be ignored. It is just stating that the IP core was made with a different board.  Here is the resource center for the Pmod ESP3. Here is the Getting Started with Digilent Pmod IPs tutorial.