Mike Boich

  • Content Count

  • Joined

  • Last visited

  1. Mike Boich

    USB errors

    I now believe the USB errors were caused by using a suspect fsbl, rather than the one that Petalinux generated. I'm still having some issues, but I believe they are now related to the extra power used by the wifi module, and not quite tolerated by my dc power supply.
  2. Mike Boich

    USB errors

    I've had reliability problems with 4 different usb wi-fi adapters running Petalinux on my Cora board. I finally realized that the problem seems to be in the USB communications between the wifi device and the host. Occasionally, I see messages like this: usb 1-1: new full-speed USB device number 4 using ci_hdrc usb 1-1: device descriptor read/64, error -110 Any suggestions on how to debug? I don't have any experience debugging USB. - Mike
  3. Now I see that you are correct, but that I had to enable certain other networking options before the menu items I needed would actually appear in the kernel menuconfig. Thanks.
  4. Thanks, but I as said in my original post, the only item in the kernel menuconfig doesn't seem to do the trick.
  5. I have a project on a Digilent Cora-Z7-10 board, and would like to use a wireless USB device that is based on the Realtek 8192cu. I see that this rtl8192cu module exists in the linux 4.9 source tree, but I'm not sure how to get Petalinux to build/include it. I'm using Petalinux 2017_4, since that's the version supported by Digilent's BSP.) When I do a "petalinux-config -c" kernel, there's an entry under DeviceDrivers/Network Device Support/Wireless LAN/Realtek Devices. I enabled this option, but the description says that this doesn't directly affect the kernel, but causes the co
  6. I decided to bite the bullet and use the Digilent BSP and Petalinux 2017.4. It was easier than I anticipated. My app uses openamp, and all of the accesses to the programmable fabric are done through the baremetal firmware running on processor #1. So the only device tree modifications to the Digilent BSP were the ones that make the echo-test app work. I didn't even change the location of the shared memory area, since the address on the Zybo version (0x3e000000) aliases down to 0x1e000000, which works perfectly. I wish everything were ported to 2018.2, but I appreciate that keeping
  7. I'm trying to migrate a project from the Zybo Z7 to Cora Z7-10. For the Zybo, I was able to use my own Vivado project (which included the TTC and other required elements), and then create a project in petalinux using the zynq template, do a "petalinux-config --get-hw-description <my-design>, build, package, and boot from the resulting SD card. When I try the same thing on the Cora it fails. (Doesn't even get as far as loading my FPGA bitstream). I can get the Digilent Cora BSP package to boot, but that appears to require that I use Petalinux 2017.4, and all the
  8. Thanks Jon. I decided to just create a new project with the custom hardware that I need (including the linux requirements like TTC, etc.), and was able to get through the workflow and produce a working kernel. Now I'm making my way through the UIO stuff! Mike
  9. I'm have a project up and running on bare-metal, and want to put it on top of embedded linux. I'm assuming I should start with your base hw configuration and that add my custom hardware to that, but I'm having trouble getting Vivado to open the project. I assume that I need to use Petalinux 2017.4 and Vivado 2017.4, since those are the tool versions that were used to create your base config. I've cloned the Zybo-Z7-20-base-linux project folder. I then to try to invoke Vivado with the "create_project.tcl" script as a command-line argument, and I get an error. The error is: "ERROR: [Pr