搜索the Community

I am trying to use the PmodCAN module together with PetaLinux on the ZedBoard, to display a CAN interface within the OS. So far I can make it show up in the interface overview with the following device tree overlay: /* /project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi */ /include/ "system-conf.dtsi" / { osc: can_osc { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <20000000>; }; }; &gpio0 { #interrupt-cells = <2>; interrupt-controller; }; &spi1 { is-decoded-cs = <0>; num-cs = <1>; status = "okay"; spidev@0x00 { compatible = "microchip,mcp25625"; spi-max-frequency = <10000000>; clocks = <&osc>; interrupt-parent = <&gpio0>; interrupts = <0 0x2>; reg = <0>; } }; I can even send and receive messages using `candump` and `cansend`, but the interface behaves strange together with some CAN libraries. E.g. Messages are sometimes not sent, when the library tries to send multiple messages without any delay between them. On the other hand, when I connect the PmodCAN to a RaspberryPi and use same said libraries, everything works fine. So the only difference I can see between the working Raspberry Pi and the "strange" behaving Zynq setup, is the manually defined device tree overlay you see above. Long story short: Is my device tree overlay for the PmodCAN correct, to use it together with the ZedBoard on the JE Pmod connector? Maybe there is even a template somewhere? Based on the issues I have, I suspect something might be wrong with the clock and frequency definitions ...

嗨，我目前正在使用PMODCAN模块，我正在尝试在其他Axi IPS的更大设计中使用它。不幸的是，我找不到有关PMODCAN Vivado IP和AXI地址空间的任何文档。因此，我有一些问题：1。对我来说还不清楚，`axi_lite_gpio'接口的用例是什么。据我所知，PMOD接口是预定的，用于与MCP25625 IC的SPI通信；其他SPI PMOD似乎也不需要它。我怀疑某些MCP25625引脚可以以某种方式配置为GPIO，但是我认为有意义的任何东西都与您提供的C代码示例不符。这把我带到了第二个问题。2.是否有有关AXI地址空间以及如何使用它来配置，发送和接收消息的文档？我目前正在尝试通过查看信号和VHDL代码来了解IP的工作方式。不幸的是，这种方法非常耗时，如果有关于地址空间的任何文档，我可以更快地完成事情。 Maybe I am just overlooking something here. To summarize, I would like to ask, if the intention behind the Vivado IP was primarily for demo purposes to use it from C code or not; should I rather implement my own IP to let it directly communicate with other AXI IPs?

您好，刚刚购买了DMC60C并试图开始。我不是在第一或机器人控件中使用它，而是想使用罐头消息来控制直流电机。我确认DMC60C可与PWM输入一起使用。我现在正在努力使CAN通信工作。我在汽车行业中，我正在使用ATI Vision和Kvaser Leaf Light发送CAN消息。从文档看来我应该将0x00000240作为29位标识符发送。我正在发送消息，但是DMC60C正在交替闪烁的红灯，表明它看不到。要确认有我可以有一个矢量VN1630，我正在监视can网络，看到消息正在发送。我附上了一个布局的框图。我认为我必须误解将消息发送到DMC60C的内容或如何发送。 Also attached is a screen shot of the message I am sending. I have tried sending messages with 4 and 8 bytes of data, sending all 0's and with Device Type 2 and Manufacturer Encoding 6. Anyway I send I get no indication the DMC60C acknowledges any CAN message. Any help would be greatly appreciated. Thanks

I am able to capture a CAN message using the logic analyzer with a "Simple" trigger of falling edge on the TX line (polarity low), but have not succeeded in triggering using the "Protocol" trigger. Attached is a screenshot of a transmit capture using "Simple" and the waveform looks correct. However when I use the attached "Protocol" settings, the analyzer never triggers. What am I missing?

我有一个较旧的Cerebot董事会之一，应该等同于目前要出售的Diglent Pro MX7嵌入式系统培训板。我想使用模拟发现模块和波形软件捕获可以捕获可以交通的。我有两个基本问题。在研究了这个论坛上的相关帖子之后，我深信模拟发现和波形软件更适合连接到收发器（RX和TX）的“ PIC侧”（RX和TX），而不是可以侧面，Canh和Canl是差异的。信号。（1）这是正确的吗？在研究了Cerebot示意图和参考手册后，看来我无法直接连接到CAN1或CAN2的RX和TX。但是，看来，如果我将JP1和所有三个JP2的所有三个引脚组合在一起，那么CAN1的RX和TX将在Connector JF的第1和4上可用。据我所知，将所有三个销钉都放在一起不会创造出电气短，因为板上的任何东西都没有驱动JP1和JP2的外针。（2）这是正确的吗？ Thanks!

I am looking at the DMC60c CAN protocol guide and also the software API reference manual. What are the API numbers needed in the CAN message to communicate with the DMC60c. For example if I wanted to send a voltage command using the function driveVoltage, what should go in the API field (Byte 1) of the message identifier? Thanks, matt

Hello, I am using a couple of DMC60C with an NI-XNET USB 8502. I have had some good luck but am running into a very specific question. The control message: 0x02060000 Uses a signed 24-bit integer for both closed loop velocity and closed loop position control setpoints. However, the makeup of that value is only loosely described in the documentation. My questions are: 1) is the byte order as shown in the manual correct? It appears strange to go trgtH in byte 3, targtL in bye 4, and trgtM in byte 5. I could understand H, M, L or L, M, H but it seems oddly shuffled as presented. 2) is a negative 24 bit value stored as 2's complement? Thank you for any advice. My motor does not appear to like the values I have been sending for velocity control mode. Sincerely, Brian