Re: MCP2518FD : Failed to detect MCP2518FD (osc=0x00000000)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Folks,

Embarrassing ...

There was a small build of 5. There was an hw change afterwarts regardging CS. Reworked 4/5. I got the one without rework but special "local" working test software.
I wonder why switching to master is not working ...

Sorry for your time lapse.

BR
Niels






Marc Kleine-Budde schrieb am 31.01.2022 15:17 (GMT +00:00):

> On 31.01.2022 15:15:03, petter@xxxxxxxxxx wrote:
>>
>> Hi Marc,
>>
>> CS = High (de-asserted, slave not selected)
>> CS = low (asserted, slave selected)
>>
>> I also did not like the 0/1 starting point, but it is defined here:
>>
>>         aliases {
>>                 gpio0 = &gpio1;
>>                 gpio1 = &gpio2;
>>                 gpio2 = &gpio3;
>>                 ...
>>
>>
>>
>> &gpio1 3 = gpiochip0 = 0*32 + 3 = gpio3
>> &gpio5 1 = gpiochip4 = 4*32 + 1 = gpio129
> 
> In your output of /sys/kernel/debug/gpio, gpiochip3 starts at 128:
> 
>>> gpiochip3: GPIOs 128-159, parent: platform/30240000.gpio, 30240000.gpio:
>>>  gpio-128 (                    |cd                  ) in  hi IRQ ACTIVE LOW
>>>  gpio-129 (                    |spi1 CS0            ) out hi ACTIVE LOW
> 
> Here it looks like this:
> 
> gpiochip4: GPIOs 128-159, parent: platform/20ac000.gpio, 20ac000.gpio:
>  gpio-130 (EIM_A25             |user1               ) out lo ACTIVE LOW
>  gpio-133 (GPIO5_05            )
>  gpio-134 (GPIO5_06            |reset               ) out lo
>  gpio-135 (GPIO5_07            )
>  gpio-136 (GPIO5_08            )
>  gpio-137 (CSPI2_CS1           |spi1 CS1            ) out hi ACTIVE LOW
>  gpio-138 (CSPI2_MOSI          )
>  gpio-139 (CSPI2_MISO          )
>  gpio-140 (CSPI2_CS0           |spi1 CS0            ) out hi ACTIVE LOW
>  gpio-141 (CSPI2_CLK           )
> 
>> Interresting with ACTIVE HIGH / LOW. cat debug/gpio tells me "ACTIVE
>> LOW" but anyway I did not see CS toggle at all. Also tested "1" but
>> nothing changed.
>>
>> By the way, the old kernel is working with the new device tree.
>>
>> I did a make clean and make sure that I really use latest build
>> artefacts. Everything is okay. Still failure.
>>
>> Maybe there are problems when using "make imx_v7_defconfig" ...
>> possible conflicts between drivers because there are much changes
>> between 5.4 and 5.10 whats enabled and/or new by default ? Try to go
>> with a very small kernel.
> 
> There shouldn't be any conflicts between drivers.
> 
> regards,
> Marc
> 
> --
> Pengutronix e.K.                 | Marc Kleine-Budde           |
> Embedded Linux                   | https://www.pengutronix.de  |
> Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
> Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |
> 



[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux