I plan to use the Cheetah SPI Host Adapter  and the Cheetah Software API (Python) for generating SPI signals to communicate with my board. Before I get started, can you tell me about timing delays from the API execution call to the signals generated at the Cheetah output?

We purchased an Aardvark I2C/SPI Host Adapter for our product development and manufacturing evaluation. We ‘re trying to use this adapter with the Flash Center Software to program 129 bytes to an ST Micro M24C02-W I2C EEPROM.  Our problem - it consistently fails with a “Slave NACK” error.

I need a protocol analyzer to capture MDIO bus transactions. I have a Total Phase 10-Pin Grabber Split Cable on hand, but I don’t see any markings for MDC and MDIO signals. Which pins should I use, and which Beagle protocol analyzer do you recommend?

I am new and suddenly immersed with programming embedded devices. I need to quickly program the N25Q256A flash chip.  I’ll be using the Cheetah SPI Host Adapter with Cheetah Software API. For this project, I need to change the 3-bit address programming sequence to a 4-bit address programming sequence. Can you help me get started?

I want to connect to multiple slave devices. With the Aardvark I2C/SPI Host Adapter, I would like to use an analog switch to make or break the connection to the slave devices chip select(CS), along with pull-ups. Do you have a recommended method for interfacing to multiple SPI slave devices?

My consulting firm just got a large contract. We’ll be testing and verifying a setup for high volume sales for airport stakeholders.  The system consists of a cash register, a tablet, and printer, and connectivity to the server farm. To better monitor transactions and provide real-time information, this project is moving the data exchange from an RS232 bus to a high-speed USB bus. Here’s a diagram of what we’ll be testing.

For a communication scenario, I am using the Aardvark Software API for data transactions. Here is the call that I am using:

I have the Advanced Cable Tester running tests on two identical working USB Type-C cables. The report shows one cable passed everything on the physical wiring section, but the other cable failed the physical wiring on SBU1 and SBU2. I have checked all wiring and function of these two cables to make sure they are working the same. Can you explain these test results?