Activity
From 01/06/2016 to 02/04/2016
02/01/2016
- 10:49 AM Software Development: RE: Spidev issues
- Fred, I'm not sure what is wrong. Perhaps if you sent us your schematic someone could look it over.
I'm pretty su...
01/29/2016
- 03:08 PM Software Development: RE: Spidev issues
- A single IOCTL call with len=4 returns 4 bytes of 0 value instead of 2 with no difference in the SPI signals.
- 12:04 PM Software Development: RE: Spidev issues
- I believe you want a single IOCTL. See the attached source code duplex method.
Example usage... - 11:51 AM Software Development: RE: Spidev issues
- Correction in above code
fd = open(devname, O_RDWR|O_SYNC);
should be
fd = open(devname, O_RDWR); - 11:49 AM Software Development: RE: Spidev issues
- This is based on spidev_test.c and other examples. There are two devices on the bus that have to be configured to re...
- 11:06 AM Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Yes, I am looking at all the SPI0 signals on a scope, and they are correct. The transmitted da... - 11:02 AM Software Development: RE: Spidev issues
- Yes, I am looking at all the SPI0 signals on a scope, and they are correct. The transmitted data is configuring the ...
- 10:44 AM Software Development: RE: Spidev issues
- Fred Frantz wrote:
> The data is now being clocked out correctly, and the device is responding with the correct da... - 10:42 AM Software Development: RE: Spidev issues
- Fred Frantz wrote:
> Mike, are you referring to the .d0_is_mosi parameter in the ompa2_mcspi_device_config structure... - 10:36 AM Software Development: RE: Spidev issues
- Mike, are you referring to the .d0_is_mosi parameter in the ompa2_mcspi_device_config structure? That is set to 1, b...
01/28/2016
- 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 troubl...
- 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 .controlle... - 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 ...
01/26/2016
- 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 ... - 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 drive... - 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.
... - 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 misinterpretati...
- 11:44 AM Software Development: RE: Spidev issues
- Jonathan Cormier wrote:
> For your case you just need to erase the kernel section.
> @nand erase 0x340000 0x50000... - 11:43 AM Software Development: RE: Spidev issues
- > U-Boot# tftp 0x82000000 $serverip:uImage
> U-Boot# nand write.i 0x82000000 0x340000 $filesize
> No errors are rep... - 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 k...
- 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 init...
- 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.
Interes... - 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 rel...
01/25/2016
- 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:...
- 04:21 PM Software Development: RE: Spidev issues
- I added the boot log for the ECC errors also.
- 03:39 PM Software Development: RE: Spidev issues
- Hope this helps.
- 03:15 PM Software Development: RE: Spidev issues
- Can you attach the bootlog for the device?
- 03:09 PM Software Development: RE: Spidev issues
- It looks like it is enabled to me.
... - 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...
- The dev kit baseboard file has been modified to include a "spidev" device, and the kernel was compiled to include the...
01/21/2016
- 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
- 05:05 PM Software Development: RE: SocketCAN configuration
- Apparently the filesystem ip utility isn't using busybox....
- 04:37 PM Software Development: RE: SocketCAN configuration
- It would be the busybox that comes in the TI filesystem we ship with the devkits....
- 04:32 PM Software Development: RE: SocketCAN configuration
- Thanks for the quick response. What version of busybox are you using?
Thanks,
Fred - 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... - What is the recommended method for configuring a socketCAN port on the MitySOM3354? I have tried using the iproute2 u...
Also available in: Atom
Go to top
