I'm using TI DSP Keystone II device for 10G Ethernet service.
The 10G interface is connected to Marvell 10G PHY device.
What I'm going to try is to use GPIO on the DSP device to access 10G PHY clause 45 management port, instead of using 10G MDIO on DSP.
Is there anyone who tried to do this? or even just implemented 1G/10G MDIO function in software?
Related
I have a Coral Dev board acquired 4/19 and activated 4/22. I purchased a ViewSonic VA1655 15.6 Inch 1080p Portable IPS Monitor with Mobile Ergonomics, USB-C and Mini HDMI for Home and Office which I power from the USB port on my 120v household power strip. (I also pimped out my Coral board with a Samsung Electronics (MZ-V8V500B/AM) 980 SSD 500GB - M.2 NVMe Interface Internal Solid State Drive with V-NAND Technology inside a SABRENT USB 3.2 Type-C Tool-Free Enclosure for M.2 PCIe NVMe and SATA SSDs (EC-SNVE) for some Gentoo chroot experiments ).
The problem I face is that if I have a crash or power down, when I try to restart by unplugging and plugging back in Coral's transformer, boot-up will not start unless I also power down the ViewSonic monitor. I believe the monitor's being "on" probably sets a voltage on the Coral board which interferes with the logic of detecting power off/power on for the reboot. Maybe I'm wrong in theory, but I would like to be able to reboot/start up Coral by plugging/unplugging the Coral's transformer and not to also have to power off the ViewSonic and then power the ViewSonic after Coral has started. Is there a configuration setting that can accomplish this?
everybody:
Now, I'm using Beagleboneblack board with bone-debian-9.4-lxqt-armhf-2018-06-17-4gb.img, and I have a touchscreen chip that is TSC2013 with I2C interface, I want to use this chip drive a LCD(800x600),but I failed, I want to know what is wrong with my I2C, who can help me?
Thanks a lot.
Your question is extremely vague in terms of what you've attempted so far and what your problems are.
You have to do a bit of work to ensure that i2c is functioning properly on your BBB.
You should follow this tutorial
If there are no active i2c ports, then you have to look into changing the uEnv.txt file to tell the BBB to activate an i2c port when it boots.
Once you have enabled your desired i2c port. Then use i2c-tools to fully debug the active i2c port.
Here is a very good tutorial about the basics of setting up i2c on the BBB
Please anyone explain the exact differences?
While implemntin the driver code, I have facing an issue in both places.
We will need more information for getting to the root of your issue. What exact problem you are facing. Well as per your query different types of driver details are given below.
Physical Device Driver: A physical device driver is a driver for a specific piece of hardware. This drivers are written by device vendor. Some of the examples are ethernet drivers, graphics drivers(intel, nvidia) etc
Logical Device Driver: A logical device driver is a high level abstraction of how a device behaves. The logical device driver talks to the physical device driver for you to keep you abstracted from the underlying hardware. So Logical device drivers are written by operating system vendor. some of the examples are generic drivers provided by microsoft like USB etc
Virtual Device Driver: Virtual device drivers are drivers which emulates a hardware device. It emulates a piece of harware, so that softwares can have illusion of accessing real hardware. Some of the virtual device driver examples are virtual network adapter, virtual DVD/CD drive, virtual disk device etc
I have a board (with NXP LPC1769) hosting an application and connected to the PC via USB cable. I use an application running on my PC and communication is pretty straightforward (some ASCII commands are exchanging) and working as it should be.
So, what I would like to achieve is to connect my favorite WIFI module ESP8266 using its TX/RX pins to the USB connector (D- and D+) of the NXP LPC1769 instead of my PC.
You may ask why you don't use any UART pins of the LPC1769. And my answer, I would love to. But it requires pretty much code modification which is not pleasant at this stage for me.
Pins P0.29 and P0.30 used from LPC1769 connected to USB connector.
Here is the existing schematic;
I would like to ask if this is even possible, and if possible, what are the options?
(I am inexperienced with NXP MCUs, still a work in progress, please bear with me).
Thank you.
NO my friend, it is simply not possible to connect USB serial to Rx/Tx pins of the ESP8266. First there is the hardware limitation, only asynchronous serial communication is possible with the ESP8266. That device has no USB host in it that can be programmed so there no way to do what you ask simply with that circuit. Nevertheless i would suggest implementing a simply board with a FTDI device of your choice (FT232R for example) and do the conversion from USB to asynchronous serial communication (Rx/Tx) directly.
We are developing extension board for BBB. It contains I2C RTC clock chip MCP79412. Chip is connected to I2C1 (pins P9.17,P9.18). I can't see any device on i2c-1, but I found chip EEPROM on i2c-2. When I connect it to I2C2 (P9.19,P9.20) I can access eeprom using capemgr loaded driver on bus i2c-1.
It looks like something swaped busses 1 and 2. I'm using Arch Linux with Kernel 3.8.13-35.
My uEnv.txt
optargs=loglevel=3 coherent_pool=1M capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4,BB-I2C1,BB-ADC
What could cause this strange behavior?