Activity
From 12/30/2015 to 01/28/2016
01/28/2016
- MW 12:12 PM Software Development: RE: Spidev issues
- I think there is also a control for the McSPI that can swap the din / dout pins between "d0" and "d1". We had trouble with this in the past.
-Mike - JC 12:06 PM Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Thanks for the correction. Setting the .bus_num = 1 solved the module issue, and the .controller_data information is required for the spi0_d0 line to be used as MOSI.
> ...
It should be correct. If data is coming... - FF 11:59 AM Software Development: RE: Spidev issues
- Thanks for the correction. Setting the .bus_num = 1 solved the module issue, and the .controller_data information is required for the spi0_d0 line to be used as MOSI.
The data is now being clocked out correctly, and the device is re...
01/26/2016
- JC 05:02 PM Software Development: RE: Spidev issues
- Fred Frantz wrote:
> After erasing the NAND, the ECC errors are resolved. Thanks, that was a self inflicted problem due to misinterpretation of our documentation.
Glad that helped.
> ...
The SOM is using the spi1 bus to talk to the NO... - JC 04:54 PM Software Development: RE: Spidev issues
- Michael Williamson wrote:
> SPIDEV sits on top of McSPI. It's an abstraction layer on top of the specific SPI driver. That may be the problem.
What Mike said. The McSPI driver is necessary for the spidev driver to work.
> ...
He h... - MW 03:49 PM Software Development: RE: Spidev issues
- SPIDEV sits on top of McSPI. It's an abstraction layer on top of the specific SPI driver. That may be the problem.
You may need to configure (either via a platform file or via device tree) a SPIDEV device that is attached to a speci... - FF 03:36 PM Software Development: RE: Spidev issues
- After erasing the NAND, the ECC errors are resolved. Thanks, that was a self inflicted problem due to misinterpretation of our documentation.
Can the McSPI conflict with SPIDEV if both are trying to access the same port? Disabling Mc... - JC 11:44 AM Software Development: RE: Spidev issues
- Jonathan Cormier wrote:
> For your case you just need to erase the kernel section.
> ...
Do double check my math on this, if wrong it could erase part of your filesystem image.
- JC 11:43 AM Software Development: RE: Spidev issues
- > U-Boot# tftp 0x82000000 $serverip:uImage
> ...
By writing the nand like this without erasing, you will corrupt the image stored including the ECC. Nand flash must be erased before writing to it.
Note in the following guide I erase ... - FF 11:17 AM Software Development: RE: Spidev issues
- The kernel and environment were reloaded just to get to a known point where everything was working previously. The kernel is being loaded via tftp.
U-Boot# tftp 0x82000000 $serverip:uImage
U-Boot# nand write.i 0x82000000 0x340000 $... - JC 10:39 AM Software Development: RE: Spidev issues
- Just checked and the 0x340000 address the ECC errors mention is the location of the kernel not the environment I initially assumed. How are you loading the kernel to boot the system if loading it from nand isn't working (tftp)? How are...
- JC 09:35 AM Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Thanks for the suggestions, but ZCAT on the target indicates that SPIDEV is enabled.
Interesting. My troubleshooting steps when trying to diagnose a driver not loading is the following.
* Check the boot log for ... - FF 09:13 AM Software Development: RE: Spidev issues
- Thanks for the suggestions, but ZCAT on the target indicates that SPIDEV is enabled. Regarding the ECC errors, I reloaded an earlier version of the kernel and an environment variable file that was working without any problems, but the E...
01/25/2016
- JC 05:33 PM Software Development: RE: Spidev issues
- Hmm no noticeable errors. You can double check the kernel, on the booted device for the spidev support:
- FF 04:21 PM Software Development: RE: Spidev issues
- I added the boot log for the ECC errors also.
- FF 03:39 PM Software Development: RE: Spidev issues
- Hope this helps.
- JC 03:15 PM Software Development: RE: Spidev issues
- Can you attach the bootlog for the device?
- FF 03:09 PM Software Development: RE: Spidev issues
- It looks like it is enabled to me.
- JC 01:41 PM Software Development: RE: Spidev issues
- A pinmux conflict would likely cause the device not to work but it would not affect the creation of the spidev device file.
You need to make sure that SPIDEV is enabled in the kernel. It doesn't look like it is by default. - The dev kit baseboard file has been modified to include a "spidev" device, and the kernel was compiled to include the SPI device driver for users. However, the expected /dev/spidev0.1 file is not generated. Can a pinmux conflict with o...
01/21/2016
- FF 08:56 AM Software Development: RE: SocketCAN configuration
- After the links were corrected on my system, it works using iproute2 also.
Thanks
01/20/2016
- JC 05:05 PM Software Development: RE: SocketCAN configuration
- Apparently the filesystem ip utility isn't using busybox.
- JC 04:37 PM Software Development: RE: SocketCAN configuration
- It would be the busybox that comes in the TI filesystem we ship with the devkits.
- FF 04:32 PM Software Development: RE: SocketCAN configuration
- Thanks for the quick response. What version of busybox are you using?
Thanks,
Fred - JC 03:24 PM Software Development: RE: SocketCAN configuration
- I used the busybox ip utility to configure can when I last tested it.
I found the following script which I created to configure can.
attachment:config_can.sh
See the following cantest script which is used to test can by connecting... - What is the recommended method for configuring a socketCAN port on the MitySOM3354? I have tried using the iproute2 utility as described in the TI instructions.
http://processors.wiki.ti.com/index.php/AM335X_DCAN_Driver_Guide#Building...