plazma33

Members
  • Content count

    16
  • Joined

  • Last visited

About plazma33

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. plazma33

    (PmodACL2) warnings messages in vivado

    I connected an PmodACL2 to JB pmod connector in vivado and created new clock in the zynq (100Mhz) then I connected it to the SCLK in the PmodACL2 , but it apears that there are some problems , these are the warnings at the Tcl console (the bitstream is generated but I want to know if these will cause a problem later) : Firas
  2. plazma33

    Connect accelerometre throught USB to zybo

    hello I bought a new ZYBO board so no need to look for difficult solutions Now I have other problems. -I created a petalinux project and I imported the "hw" description then builded BOOT.BIN -GOAL : booting linux on ZYBO and recognizing all the GPIOS where I will plug (GYRO, Accelerometre,Bleutooth,Leds,Buttons) -assuming that the Devitree is well configured and contains all of the GPIOS , the Petalinux RG Manual contains lots of options but I dont see at any of the steps that I should put the Devicetree alongside with BOOT.BIN and linux image in the FAT32 partition see image(1) below) RG manual link : https://www.xilinx.com/support/documentation/sw_manuals/petalinux2015_4/ug1144-petalinux-tools-reference-guide.pdf -I'm following this type of SD card structure (see image(2) below) and I think this is the good way -PS : -I already configured the SD card in two partiton (FAT32 and ext4) -the ext4 partition contains a linario filesystem -I configured the RootFS type as "SD" in the petalinux project what should I do ?? THANK YOU FOR YOUR HELP.
  3. plazma33

    petalinux Devicetree zybo

    hello -I created a petalinux project and I imported the "hw" description then builded BOOT.BIN -GOAL : booting linux on ZYBO and recognizing all the GPIOS where I will plug (GYRO, Accelerometre,Bleutooth,Leds,Buttons) -assuming that the Devitree is well configured and contains all of the GPIOS , the Petalinux RG Manual contains lots of options but I dont see at any of the steps that I should put the Devicetree alongside with BOOT.BIN and linux image in the FAT32 partition see image(1) below) RG manual link : https://www.xilinx.com/support/documentation/sw_manuals/petalinux2015_4/ug1144-petalinux-tools-reference-guide.pdf -I'm following this type of SD card structure (see image(2) below) and I think this is the good way -PS : -I already configured the SD card in two partiton (FAT32 and ext4) -the ext4 partition contains a linario filesystem -I configured the RootFS type as "SD" in the petalinux project what should I do ?? THANK YOU FOR YOUR HELP.
  4. plazma33

    Connect accelerometre throught USB to zybo

    thank your for your offer it very nice from your part , and yeah , your number reflects your generosity toword peoples , but bout the accelerometre I dont think that it can not determine an object position and here is my explenaition ( based on my mathematics and physics background) acceleration is not the only variable that throught it we can for example determinate how much a robot made x meters in one of the thre axes (x,y,z) , the other variables that are missing are : - the periode of time T spent by that robot with that acceleration A - the mass of that robot - the wheels type ==> so we get the h constant - the type of the floor ==> so we get the friction variable to calculate this is why I think using an accelerometre is quite difficult if you want to be presize with the results , For me I m using an accelerometre to count hou much a boxer punch on a punching bag is in Newtons , so if I know the wheight of the bag and the acceleration and the surface of contact I can know how much Newtons he putted into that punch . here is a video link for a small prototype of what we are going to do , it's going to be way better than it looks in the future : https://www.youtube.com/watch?v=5SkvQ-FXG3s&t=3s Firas
  5. plazma33

    Connect accelerometre throught USB to zybo

    @D@n Thank you but I prefer CMod A7 , it's more guaranty and sure Firas
  6. plazma33

    Connect accelerometre throught USB to zybo

    @D@n really ,, you where soo helpful , it's beyond working with a company , you did more then should , thank you for your help , you saved for me more than you imagine , and No it's not about promoting , you'r finding solutions so the Zybo and other digilent products become easier to manipulate . THANK YOU
  7. plazma33

    Connect accelerometre throught USB to zybo

    @D@n thank you for your fast reply , I tried to fix the Pmod problems but I failed it's a bit difficult , It's true that it looks like trying to fit a Square peg in a round hole , but I did not meant that that USBUART is the solution , I m just trying to know if there is a sort of a convertor interface from Accelerometre output to the UART port or the OGT port, is there any converters ?
  8. plazma33

    Connect accelerometre throught USB to zybo

    @D@n thank you ,, yeah all your messages are clear , I know that I can connect the Accelerometre directly to the PMOD connector on the zybo and then to the PC , BUT here is what I m doing so you'r going understand why I need the USBUART - I booted linux on the zybo so I should not use the PC even if I can , - I tried to connect the ACCELEROMETRE to the zybo throught the PMOD connectors , but it's not detected by the zybo , - after searching a lot and making lots of hardware diagnostics i found out that the PMOD connectors on the zybo are broken (several pins are broken) - i found out that the USB OGT is working and the zybo can read date throught it , ( I teste : keyboard , mouse , bleutooth dongl , wifi dongle...) -I decided to read data from the ACCELEROMETRE throught the USB port on the zybo ( which is the OGT as you told me) So I think that my problem is cleare now ! I will be soo greatful if you find a solution for me
  9. plazma33

    Connect accelerometre throught USB to zybo

    @D@n thank you for the information , I m trying to connect a "Pmod ACL: 3-axis Accelerometer" to my zybo board throught a USB port (UART or OGT) , so I m looking for a solution , I found something that might help me wich is the "Pmod USBUART: USB to UART Interface" so i can plug the Accelerometre to the USBUART and then plug the USBUART into the ZYBO throught a USB port , can you guide me ?? , if what I m talking about is a solution , then is it the only one ? because I have to perchase the USBUART and that will take time. here is both the USBUART and the ACCELEROMETER . http://store.digilentinc.com/pmod-usbuart-usb-to-uart-interface/ http://store.digilentinc.com/pmod-acl-3-axis-accelerometer/
  10. hello , I have a linux ubuntu on my zybo board and I m going to use an accelerometre , So can I connect it throught UART USB instead of Gpio port ? please help
  11. plazma33

    describ external GPIOS in zynq-zybo.dts

    I generate a bitstream and exported the heardware to SDK , and I m stack in this step "import the hardware configuration (.hdf) by following pg. 25 of RG. for petalinux" there are 3 .hdf files in my project and I tried them all , but it's always the same error : (Failed to locate the Vivado export to SDK directory, please make sure the directory directory exists! Configures the project or the specified component with menuconfig.) I m sure I imported the hardware in a good way ( see picture 1) picture (2,3,4) resume the my attempts using petalinuc-configure command with thoes 3 repositories containing .hdf files
  12. plazma33

    describ external GPIOS in zynq-zybo.dts

    @sbobrowicz I m soo happy that you deployed soo much time and effort to answer me , I will go back here as soon as I finich your instructions !
  13. plazma33

    describ external GPIOS in zynq-zybo.dts

    HI @yohboy thank you for the link you shared , but I have problems generation DTS file with SDK , I m using the zybo-base-system-deseign provided in Digilent website , i will be soo happy if I can find a ready to implement DTS or DTB related to the zybo-base-system deseign..
  14. plazma33

    describ external GPIOS in zynq-zybo.dts

    Hi @yohboy thank you , yes I have only one GPIO ,,, I m not working without Vivado , I think there is a relation between Vivado and DTS file but I choosed to work only with kernel drivers So I m looking forward to find a full DTS file and compile it so I can find all the drivers then I can controle all the peripheral leds buttons and Pmods !! Please I need help !!!! here is my DTS file : zynq-zybo.dts : /dts-v1/; / { #address-cells = <1>; #size-cells = <1>; compatible = "xlnx,zynq-7000"; model = "Xilinx Zynq"; aliases { ethernet0 = &ps7_ethernet_0; serial0 = &ps7_uart_1; spi0 = &ps7_qspi_0; } ; chosen { bootargs = "console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait"; linux,stdout-path = "/amba@0/serial@e0001000"; } ; cpus { #address-cells = <1>; #size-cells = <0>; ps7_cortexa9_0: cpu@0 { bus-handle = <&ps7_axi_interconnect_0>; clock-latency = <1000>; clocks = <&clkc 2>; compatible = "arm,cortex-a9"; device_type = "cpu"; interrupt-handle = <&ps7_scugic_0>; operating-points = <666667 1000000 333334 1000000 222223 1000000>; reg = <0x0>; } ; ps7_cortexa9_1: cpu@1 { bus-handle = <&ps7_axi_interconnect_0>; clocks = <&clkc 2>; compatible = "arm,cortex-a9"; device_type = "cpu"; interrupt-handle = <&ps7_scugic_0>; reg = <0x1>; } ; } ; pmu { compatible = "arm,cortex-a9-pmu"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 5 4>, <0 6 4>; reg = <0xf8891000 0x1000>, <0xf8893000 0x1000>; reg-names = "cpu0", "cpu1"; } ; ps7_ddr_0: memory@0 { device_type = "memory"; reg = <0x0 0x20000000>; } ; ps7_axi_interconnect_0: amba@0 { #address-cells = <1>; #size-cells = <1>; compatible = "xlnx,ps7-axi-interconnect-1.00.a", "simple-bus"; ranges ; ps7_afi_0: ps7-afi@f8008000 { compatible = "xlnx,ps7-afi-1.00.a"; reg = <0xf8008000 0x1000>; } ; ps7_afi_1: ps7-afi@f8009000 { compatible = "xlnx,ps7-afi-1.00.a"; reg = <0xf8009000 0x1000>; } ; ps7_afi_2: ps7-afi@f800a000 { compatible = "xlnx,ps7-afi-1.00.a"; reg = <0xf800a000 0x1000>; } ; ps7_afi_3: ps7-afi@f800b000 { compatible = "xlnx,ps7-afi-1.00.a"; reg = <0xf800b000 0x1000>; } ; ps7_ddrc_0: ps7-ddrc@f8006000 { compatible = "xlnx,zynq-ddrc-1.0"; reg = <0xf8006000 0x1000>; xlnx,has-ecc = <0x0>; } ; ps7_dev_cfg_0: ps7-dev-cfg@f8007000 { clock-names = "ref_clk", "fclk0", "fclk1", "fclk2", "fclk3"; clocks = <&clkc 12>, <&clkc 15>, <&clkc 16>, <&clkc 17>, <&clkc 18>; compatible = "xlnx,zynq-devcfg-1.0"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 8 4>; reg = <0xf8007000 0x100>; } ; ps7_dma_s: ps7-dma@f8003000 { #dma-cells = <1>; #dma-channels = <8>; #dma-requests = <4>; clock-names = "apb_pclk"; clocks = <&clkc 27>; compatible = "arm,primecell", "arm,pl330"; interrupt-names = "abort", "dma0", "dma1", "dma2", "dma3", "dma4", "dma5", "dma6", "dma7"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 13 4>, <0 14 4>, <0 15 4>, <0 16 4>, <0 17 4>, <0 40 4>, <0 41 4>, <0 42 4>, <0 43 4>; reg = <0xf8003000 0x1000>; } ; ps7_ethernet_0: ps7-ethernet@e000b000 { #address-cells = <1>; #size-cells = <0>; clock-names = "ref_clk", "aper_clk"; clocks = <&clkc 13>, <&clkc 30>; compatible = "xlnx,ps7-ethernet-1.00.a"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 22 4>; phy-handle = <&phy0>; phy-mode = "rgmii-id"; reg = <0xe000b000 0x1000>; xlnx,eth-mode = <0x1>; xlnx,has-mdio = <0x1>; xlnx,ptp-enet-clock = <108333336>; mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@1 { compatible = "realtek,RTL8211E"; device_type = "ethernet-phy"; reg = <1>; } ; } ; } ; ps7_globaltimer_0: ps7-globaltimer@f8f00200 { clocks = <&clkc 4>; compatible = "arm,cortex-a9-global-timer"; interrupt-parent = <&ps7_scugic_0>; interrupts = <1 11 0x301>; reg = <0xf8f00200 0x100>; } ; ps7_gpio_0: ps7-gpio@e000a000 { #gpio-cells = <2>; clocks = <&clkc 42>; compatible = "xlnx,zynq-gpio-1.0"; emio-gpio-width = <64>; gpio-controller ; gpio-mask-high = <0xc0000>; gpio-mask-low = <0xfe81>; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 20 4>; reg = <0xe000a000 0x1000>; } ; ps7_iop_bus_config_0: ps7-iop-bus-config@e0200000 { compatible = "xlnx,ps7-iop-bus-config-1.00.a"; reg = <0xe0200000 0x1000>; } ; ps7_ocmc_0: ps7-ocmc@f800c000 { compatible = "xlnx,zynq-ocmc-1.0"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 3 4>; reg = <0xf800c000 0x1000>; } ; ps7_pl310_0: ps7-pl310@f8f02000 { arm,data-latency = <3 2 2>; arm,tag-latency = <2 2 2>; cache-level = <2>; cache-unified ; compatible = "arm,pl310-cache"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 2 4>; reg = <0xf8f02000 0x1000>; } ; ps7_qspi_0: ps7-qspi@e000d000 { clock-names = "ref_clk", "pclk"; clocks = <&clkc 10>, <&clkc 43>; compatible = "xlnx,zynq-qspi-1.0"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 19 4>; is-dual = <0>; num-cs = <1>; reg = <0xe000d000 0x1000>; xlnx,fb-clk = <0x1>; xlnx,qspi-mode = <0x0>; #address-cells = <1>; #size-cells = <0>; flash@0 { compatible = "n25q128"; reg = <0x0>; spi-tx-bus-width = <1>; spi-rx-bus-width = <4>; spi-max-frequency = <50000000>; #address-cells = <1>; #size-cells = <1>; partition@qspi-fsbl-uboot { label = "qspi-fsbl-uboot"; reg = <0x0 0x400000>; }; partition@qspi-linux { label = "qspi-linux"; reg = <0x400000 0x500000>; }; partition@qspi-device-tree { label = "qspi-device-tree"; reg = <0x900000 0x20000>; }; partition@qspi-user { label = "qspi-user"; reg = <0x920000 0x6E0000>; }; }; } ; ps7_qspi_linear_0: ps7-qspi-linear@fc000000 { clock-names = "ref_clk", "aper_clk"; clocks = <&clkc 10>, <&clkc 43>; compatible = "xlnx,ps7-qspi-linear-1.00.a"; reg = <0xfc000000 0x1000000>; } ; ps7_scugic_0: ps7-scugic@f8f01000 { #address-cells = <2>; #interrupt-cells = <3>; #size-cells = <1>; compatible = "arm,cortex-a9-gic", "arm,gic"; interrupt-controller ; num_cpus = <2>; num_interrupts = <96>; reg = <0xf8f01000 0x1000>, <0xf8f00100 0x100>; } ; ps7_scutimer_0: ps7-scutimer@f8f00600 { clocks = <&clkc 4>; compatible = "arm,cortex-a9-twd-timer"; interrupt-parent = <&ps7_scugic_0>; interrupts = <1 13 0x301>; reg = <0xf8f00600 0x20>; } ; ps7_scuwdt_0: ps7-scuwdt@f8f00620 { clocks = <&clkc 4>; compatible = "xlnx,ps7-scuwdt-1.00.a"; device_type = "watchdog"; interrupt-parent = <&ps7_scugic_0>; interrupts = <1 14 0x301>; reg = <0xf8f00620 0xe0>; } ; ps7_sd_0: ps7-sdio@e0100000 { clock-frequency = <50000000>; clock-names = "clk_xin", "clk_ahb"; clocks = <&clkc 21>, <&clkc 32>; compatible = "arasan,sdhci-8.9a"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 24 4>; reg = <0xe0100000 0x1000>; xlnx,has-cd = <0x1>; xlnx,has-power = <0x0>; xlnx,has-wp = <0x1>; } ; ps7_slcr_0: ps7-slcr@f8000000 { #address-cells = <1>; #size-cells = <1>; compatible = "xlnx,zynq-slcr", "syscon"; ranges ; reg = <0xf8000000 0x1000>; clkc: clkc@100 { #clock-cells = <1>; clock-output-names = "armpll", "ddrpll", "iopll", "cpu_6or4x", "cpu_3or2x", "cpu_2x", "cpu_1x", "ddr2x", "ddr3x", "dci", "lqspi", "smc", "pcap", "gem0", "gem1", "fclk0", "fclk1", "fclk2", "fclk3", "can0", "can1", "sdio0", "sdio1", "uart0", "uart1", "spi0", "spi1", "dma", "usb0_aper", "usb1_aper", "gem0_aper", "gem1_aper", "sdio0_aper", "sdio1_aper", "spi0_aper", "spi1_aper", "can0_aper", "can1_aper", "i2c0_aper", "i2c1_aper", "uart0_aper", "uart1_aper", "gpio_aper", "lqspi_aper", "smc_aper", "swdt", "dbg_trc", "dbg_apb"; compatible = "xlnx,ps7-clkc"; fclk-enable = <0xf>; ps-clk-frequency = <50000000>; reg = <0x100 0x100>; } ; } ; ps7_ttc_0: ps7-ttc@f8001000 { clocks = <&clkc 6>; compatible = "cdns,ttc"; interrupt-names = "ttc0", "ttc1", "ttc2"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 10 4>, <0 11 4>, <0 12 4>; reg = <0xf8001000 0x1000>; } ; ps7_uart_1: serial@e0001000 { clock-names = "uart_clk", "pclk"; clocks = <&clkc 24>, <&clkc 41>; compatible = "xlnx,xuartps", "cdns,uart-r1p8"; current-speed = <115200>; device_type = "serial"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 50 4>; port-number = <0>; reg = <0xe0001000 0x1000>; xlnx,has-modem = <0x0>; } ; ps7_usb_0: ps7-usb@e0002000 { clocks = <&clkc 28>; compatible = "xlnx,ps7-usb-1.00.a", "xlnx,zynq-usb-1.00.a"; dr_mode = "host"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 21 4>; phy_type = "ulpi"; reg = <0xe0002000 0x1000>; xlnx,usb-reset = "MIO 46"; } ; ps7_xadc: ps7-xadc@f8007100 { clocks = <&clkc 12>; compatible = "xlnx,zynq-xadc-1.00.a"; interrupt-parent = <&ps7_scugic_0>; interrupts = <0 7 4>; reg = <0xf8007100 0x20>; } ; } ; } ;
  15. I finished booting linux on zybo with linario file system and I m trying to user the user space and kernel drivers to controle LEDs and get input information from peripheral buttons , gyroscope, accéléromètre and a bluetooth So I wonder if I have to insert gpios déclarations in zynq-zybo.dts and compile a new devicetree.dtb !! this are some screanshots from my zybo terminal :