krtkl / snickerdoodle-examples Goto Github PK

@krtklbush @Weatherbee
Unfortunately, I could not get the emio-spi example to work on the snickerdoodle prime.
Here is what I tried:

-> Regenerated everything in vivado 2017.4
-> Exported hardware
-> Created fsbl project in sdk using the exported hardware
-> Generated boot.img using the created fsbl.elf, bitstream and the provided u-boot.elf.

No matter what I try the result of spitest is always:

0x00 0x00 0x00 0x00

Attached, you will find my devicetree.dts (as txt for github) and the bif file (as txt). I really hope it is my fault and not a hardware issue.

Thank you.

devicetree.txt
FSBL.txt

The file snickerdoodle_GPIO/gpiotest.sh has an incorrect mapping for pin JXX.37

[32]=4 [35]=6 [36]=23 [37]=27 [38]=22)

This should be

[32]=4 [35]=6 [36]=23 [37]=7 [38]=22)

Also, the entry for the PS gpio is missing entries for J3.2 and J3.4 (aka MIO 52 and 53).

The snickerdoodle_black_GPIO/gpiotest.sh versions correct for both of these issues.

Anyone know why in Vivado2019 I get these errors? I had to attach GPIO2 from the first axi_gpio_0 to GPIO1 output and similarly from the second to GPIO3 before running synthesis and implementation. Do I need to someone specify no connects to the gpio_tri_io signals?

Which one of these is for the Snickerdoodle-one (the original)?

I tried to run a vivado project as follows for the snickerdoodle:

vivado -mode gui -project snickerdoodle_GPIO.xpr &

It needed to upgrade 5 IPs for Vivado 18.2 which I did. Then I saw some GPIO not connected and clicked the automation assistant and selected all and it connected some of them but not some of them. So, I clicked generate bitstream and I am getting the following errors. Shouldn't it work right out of the box for such a simple example. Also, I am not sure why GPIO2 and GPIO3 are not automatically connected. Any ideas, anyone?