• Content Count

  • Joined

  • Last visited

About yohboy

  • Rank
    Frequent Visitor

Recent Profile Visitors

1392 profile views
  1. Hi @bellirob, I'm happy to see someone trying to use yocto Could you explain what you've done with yocto so far ? I can't help without knowing what you've already done ! Add more details please.
  2. I'm happy it works for you, glad to help you
  3. I think your line : reg_write(ptr_axi_gpio,GPIO_GLOBAL_IRQ,0x1); is false. See page 13 of sbobrowicz link in Global Interrupt Enable Register (GIER), you must set to 1 the bit 31, so it is 0x80000000 and not 0x1.
  4. Oh I didn't notice that too, sbobrowicz is right, you forgot to configure your GPIO. There is also an example in my answer that you link in your first message !
  5. Since you have 3 cells in interrupt, it should be 3 : #interrupt-cells = <3>;
  6. Hi, I guess you have the option "uio_pdrv_genirq.of_id=generic-uio" in your bootargs too since you catch the /dev/uio*. In your device tree, it seems that you missed the interrupt-cells. You may try to add it ! https://www.kernel.org/doc/Documentation/devicetree/bindings/interrupt-controller/interrupts.txt Regards, Yohan
  7. @nickwh, I'm not familiar with Petalinux since I use directly Yocto, so I can't tell you where are those files. Maybe you can try something like "petalinux-config -c uboot". But I think it will allow you to only choose the uboot version. This link is old, but maybe will do the trick https://www.xilinx.com/support/answers/59349.html regards, Yohan
  8. @nickwh Yes, your method set MAC address in u-boot. My method set it directly in linux kernel. But if you want to read it before boot in EEPROM it is different. I don't know if you're using uboot-xlnx or directly u-boot, but in u-boot it seems CONFIG_ZYNQ_EEPROM is not set by default. See http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/zynq-common.h;h=4b6b08885134125187fb38a82a4e4a983c6483e5;hb=HEAD and : http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/zynq_zybo.h;h=808967cee331dd78380dc61e60f72c6643ea9e36;hb=HEAD I never done this before,
  9. Hi @nickwh, I remember I changed my zybo MAC address with the device-tree. In your system.dts (or system-top.dts) you should find "&ǵem0" with local-mac-address = [your address]; If this field is empty I assume you'll get a random MAC address. Let me know if it works for you ! regards, Yohan
  10. Thank you for answer. I already ordered the wilink from TI and the adaptor from avnet. It's more expensive than the PMOD wifi but it supports wifi and BLE. Yohan
  11. Hi Ciprian, I'm booting from SD, and load all the files to boot on ramdisk. So i'm not sure QSPI will be the problem, am I right ? Here the uenv.txt I use to boot : uenvcmd=set serverip && set ipaddr && tftpboot 0x2000000 uImage&& tftpboot 0x3000000 core-image-minimal-zybo-gateway.rootfs.cpio.gz.u-boot && tftpboot 0x2A00000 system.dtb && bootm 0x2000000 0x3000000 0x2A00000 But the problem seems to be before, when the spl try to load the bitstream from SD. regards, Yohan
  12. Hi, I had a problem yesterday with my zybo, I'm unable to load bitstream and boot linux on it. It was working very well. As I was not sure the problem was hardware, I took a new zybo and try to load bitstream and boot on linux. It is working. So I don't know what's the problem with my old zybo. Do you know what could be the cause ? This is the error when I try to boot: U-Boot SPL 2016.03 (May 04 2017 - 11:40:33) mmc boot
  13. Hi, Thank you for answers, the Pmod WIFI IP will help me a lot to put it on zybo without linux I guess. But I dug a little into the IP driver source code and if I want to port it on linux, it seems it will be much painful. Maybe I'm wrong. Perhaps the best solution is to change the WIFI module before it costs a lot of development time. Yohan
  14. You can find them in zynq datasheet, and also in example code for interrupt UIO. This one for example : https://forums.xilinx.com/xlnx/attachments/xlnx/ELINUX/12938/1/gpio_uio_app.c
  15. Hi sg4036, I'm sorry, I forgot to give you the define :/ #define GPIO_DATA_OFFSET 0x00 #define GPIO_TRI_OFFSET 0x04 #define GPIO_DATA2_OFFSET 0x08 #define GPIO_TRI2_OFFSET 0x0C #define GPIO_GLOBAL_IRQ 0x11C #define GPIO_IRQ_CONTROL 0x128 #define GPIO_IRQ_STATUS 0x120 Maybe you won't need all the define but you'll have. Let me know if it works ! Yohan