Activity
From 07/19/2017 to 08/17/2017
08/15/2017
- Has the MitySOM-5CSX ever been involved in EMI testing? I'm getting reports from a customer that there is quite a bit of radiated noise at the DDR3 frequency range. They haven't given the details yet, but it would be great to know if y...
08/03/2017
- NH 07:25 PM Software Development: RE: Using EEPROM available on MitySOM-5CSX
- We are using kernel version 4.1.22
-Nick - MW 07:22 PM Software Development: RE: Using EEPROM available on MitySOM-5CSX
- What version of the kernel are you using? From our site? Version 3.16?
-Mike
- NH 06:58 PM Software Development: RE: Using EEPROM available on MitySOM-5CSX
- Mike,
I recently picked up this task and haven't been able to see the NOR flash device in the MTD devices list. On boot-up I get the following message:
[ 1.159717] cadence-qspi ff705000.spi: couldn't determine tshsl-ns
[ 1.1...
07/20/2017
- MW 06:09 PM Software Development: RE: I2C Slave Communication Hanging
- So I didn't respond right away as you are using verilog and I am more of a VHDL guy, but there is an open drain primitive called OPNDRN.
You can see an example of it inferred in VHDL here (bottom of file) for I2C routing like you are ... - JP 05:43 PM Software Development: RE: I2C Slave Communication Hanging
- We appear to have finally discovered the root cause of our issue. We actually had a self-inflicted bug where the SCL line on this one port was defined as "output" rather than "inout". Thus, we didn't really have the "open drain" we thoug...
07/19/2017
- JK 07:39 PM Software Development: RE: I2C Slave Communication Hanging
- Dan,
I've attached 2 scope shots between the Aardvark as master and the ST1633 as slave:
1. A single byte write with a value of 0x01
2. A subsequent single byte read, which we expect to return 0x04 (and does, in this trace)
This ... - JK 03:42 PM Software Development: RE: I2C Slave Communication Hanging
- Dan,
We'll be conducting investigations this afternoon with both the Linux I2C kernel driver and a bit-bang I2C user-space module we just finished writing. As a part of those investigations, we'll send along a read request capture bet... - DV 03:45 AM Software Development: RE: I2C Slave Communication Hanging
- Jared,
To me it looks like the scope capture you've shown should be correct and as you've said there shouldn't be a stop condition between the first and second byte, which is why the clock stays low. Though the second byte isn't ack'e...