Jump to content

Search the Community

Showing results for tags 'driver'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. Hello. Im trying to read an I2C sensor (ADXL357) with a Zybo Z7-10. Im kinda lost since im not an expert on fpgas. Im using this design on vivado 2019.2 ##Clock signal set_property -dict { PACKAGE_PIN K17 IOSTANDARD LVCMOS33 } [get_ports { sysclk }]; #IO_L12P_T1_MRCC_35 Sch=sysclk create_clock -add -name sys_clk_pin -period 8.00 -waveform {0 4} [get_ports { sysclk }]; ##Pmod Header JC set_property -dict { PACKAGE_PIN V15 IOSTANDARD LVCMOS33 } [get_ports { port_i2c_scl_io }]; #IO_L10P_T1_34 Sch=jc_p[1] set_property -dict { PACKAGE_PIN W15 IOSTANDARD LVCMOS33 } [get_ports { port_i2c_sda_io }]; #IO_L10N_T1_34 Sch=jc_n[1] ls /dev gives only i2c-0 interface. Im working with a pynq framework that uses petalinux as base. For now im not using python but im trying first to detect the sensor address (from linux) and then do the logic (python or with sdk) When i connect to the Pin 1 and 2 of the PMOD JC i dont detect nothing with "sudo i2c -r -y 0" only "--" on all the addresses. I have tried other ports but no response yet. What am i doing wrong? Is Pin 1/2 correct on JC? i dont understand why linux doesn't detect the sensor. The reference manual says that any pin can be routed throug PMOD but how do i said to the linux that P1-2 of JC is the i2c? (i have all pmods available so i can use all). Thanks EDIT: cat ./petalinux_project/build/tmp/work-shared/plnx-zynq7/kernel-source/arch/arm/boot/dts/zynq-7000.dtsi amba: amba { u-boot,dm-pre-reloc; compatible = "simple-bus"; #address-cells = <1>; #size-cells = <1>; interrupt-parent = <&intc>; ranges; ... ... i2c0: i2c@e0004000 { compatible = "cdns,i2c-r1p10"; status = "disabled"; clocks = <&clkc 38>; interrupt-parent = <&intc>; interrupts = <0 25 4>; reg = <0xe0004000 0x1000>; #address-cells = <1>; #size-cells = <0>; }; i2c1: i2c@e0005000 { compatible = "cdns,i2c-r1p10"; status = "disabled"; clocks = <&clkc 39>; interrupt-parent = <&intc>; interrupts = <0 48 4>; reg = <0xe0005000 0x1000>; #address-cells = <1>; #size-cells = <0>; }; Is I2C disabled right? what should be the device tree to enable the pins on a pmod? modifying the dts then i should recompile boot.bind and image.ub and replace it on the sd?
  2. Hi im beginner on vivado, i have some troubles to interface the pmod wifi on zybo board. have you any tutorial how to do that on zybo board ?? thanks for your response
  3. Hi Im using Zybo 7020 Vivado/Vitis 2020 and i have some errors on Vitis when i compile the hw platform. "Running Make libs in ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src" make -C ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src -s libs "SHELL=CMD" "COMPILER=arm-none-eabi-gcc" "ASSEMBLER=arm-none-eabi-as" "ARCHIVER=arm-none-eabi-ar" "COMPILER_FLAGS= -O2 -c" "EXTRA_COMPILER_FLAGS=-mcpu=cortex-a9 -mfpu=vfpv3 -mfloat-abi=hard -nosta rtfiles -g -Wall -Wextra" make[2]: Entering directory 'C:/Users/NZT/workspace/Gyrotest/zynq_fsbl/zynq_fsbl_bsp/ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src' "Compiling PmodGYRO..." arm-none-eabi-ar: *.o: Invalid argument make[2]: *** [Makefile:19: libs] Error 1 make[1]: *** [Makefile:30: ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src/make.libs] Error 2 make: *** [Makefile:30: zynq_fsbl_bsp/ps7_cortexa9_0/lib/libxil.a] Error 2 make[2]: Leaving directory 'C:/Users/NZT/workspace/Gyrotest/zynq_fsbl/zynq_fsbl_bsp/ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src' make[1]: Leaving directory 'C:/Users/NZT/workspace/Gyrotest/zynq_fsbl/zynq_fsbl_bsp' Building the BSP Library for domain - standalone_domain on processor ps7_cortexa9_0 "Running Make include in ps7_cortexa9_0/libsrc/coresightps_dcc_v1_7/src" "Compiling gpiops" "Running Make libs in ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src" make -C ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src -s libs "SHELL=CMD" "COMPILER=arm-none-eabi-gcc" "ASSEMBLER=arm-none-eabi-as" "ARCHIVER=arm-none-eabi-ar" "COMPILER_FLAGS= -O2 -c" "EXTRA_COMPILER_FLAGS=-mcpu=cortex-a9 -mfpu=vfpv3 -mfloat-abi=hard -nosta rtfiles -g -Wall -Wextra" "Compiling PmodGYRO..." arm-none-eabi-ar: *.o: Invalid argument make[1]: *** [Makefile:19: libs] Error 1 make: *** [Makefile:30: ps7_cortexa9_0/libsrc/PmodGYRO_v1_0/src/make.libs] Error 2 Failed to build the bsp sources for domain - standalone_domain Failed to generate the platform. Reason: Failed to build the zynq_fsbl application. invoked from within "::tcf::eval -progress {apply {{msg} {puts $msg}}} {tcf_send_command tcfchan#0 xsdb eval s es {{platform active Gyrotest; platform generate }}}" (procedure "::tcf::send_command" line 4) invoked from within "tcf send_command $::xsdb::curchan xsdb eval s es [list "platform active $PLATFORM_NAME; platform generate $target"]" invoked from within "if { $iswindows == 1 } { set XSDB_PORT [lindex $argv 0] set PLATFORM_NAME [lindex $argv 1] set arglen [llength $argv] set lastind..." (file "C:/Xilinx/Vitis/2020.1\scripts\vitis\util\buildplatform.tcl" line 11) I thinks there is some problems in the makefile the error comes from this line in makefile $(ARCHIVER) -r ${RELEASEDIR}/${LIB} ${OUTS} I downloaded the Library from github
  4. Hello. My project includes cmod-s7 and HS3 connected to the XC7A35T. I work on windows 10. Everything worked correctly, but sometimes the system lost connection to the devices. Reinstalling the Digilent drivers helped. The last time (today), this happened, and the reinstallation had no effect. These devices appear in the device manager, but Adept2 does not detect them. Replacing USB cables is also not effective. Any help would be greatly appreciated.
  5. At the description of the Pmod Step it says that it can drive both motors simultaneously. I want to know if it can drive them with different number of steps on each motor. So the Pmod STEP will be like an 2 in 1 driver or it can only drive identical the motors.
×
×
  • Create New...