r32.1 SDK: Two-way spican initializes normally
After updating the SDK version, Use the same MCP2515 driver and DTS
r32.4.3 SDK: one spican initialization failures
r32.1 SDK: Two-way spican initializes normally
After updating the SDK version, Use the same MCP2515 driver and DTS
r32.4.3 SDK: one spican initialization failures
dts modify as:
hardware/nvidia/platform/t19x/galen/kernel-dts/
tegra194-p2888-0001-p2822-0000.dts
/{
mcp251x_clk16MHz:mcp2515{
compatible="fixed-clock";
#clock-cells=<0>;
clock-frequency=<16000000>;
};
spi@3210000{
status = "okay";
spidev@0{
compatible = "spidev";
spi-max-frequency = <20000000>;
reg = <0>;
status = "disabled";
};
can0@0{
compatible = "microchip,mcp2515";
reg=<0x00>;
spi-max-frequency = <10000000>;
clocks=<&mcp251x_clk16MHz>;
interrupt-parent=<&tegra_aon_gpio>;
interrupts=<TEGRA194_AON_GPIO(AA, 6) IRQ_TYPE_EDGE_FALLING>;
reset-gpios = <&tegra_main_gpio TEGRA194_MAIN_GPIO(T,3) GPIO_ACTIVE_LOW>;
vdd-supply=<&vdd_usb20_5v0>;
xceiver-supply=<&vdd_usb20_5v0>;
pool_mode=<0>;
enable_dma=<1>;
status="okay";
};
};
spi@c260000{
status = "okay";/*spi2*/
spidev@0{
compatible = "spidev";
reg = <0>;
spi-max-frequency = <25000000>;
status = "disabled";
};
can0@0{
compatible = "microchip,mcp2515";
reg=<0x00>;
spi-max-frequency = <10000000>;
clocks=<&mcp251x_clk16MHz>;
interrupt-parent=<&tegra_aon_gpio>;
interrupts=<TEGRA194_AON_GPIO(BB, 0) IRQ_TYPE_EDGE_FALLING>;
//reset-gpios = <&tegra_main_gpio TEGRA194_MAIN_GPIO(T,0) GPIO_ACTIVE_LOW>;
reset-gpios = <&tegra_main_gpio TEGRA194_MAIN_GPIO(S,5) GPIO_ACTIVE_LOW>;
vdd-supply=<&vdd_usb20_5v0>;
xceiver-supply=<&vdd_usb20_5v0>;
pool_mode=<0>;
enable_dma=<1>;
status="okay";
};
};
};
Does 32.1 have show the “could not get clock” error message too?
no , 32.1 is normal
Why the status in the spi@xxx scope is disable?
It doesn’t matter because the other spican is working