I have a new Intel Edison connected to the Arduino breakout board and it is unable to boot. I have never seen it boot ever.
I have tried connecting it with different settings to discard a problem at cable level or power input.
The current setup is:
-Intel Edison mounted on Arduino breakout board.
-Power cable connected to Powered USB Hub or to wall adapter.
-Console cable connected directly to computer USB port.
When monitoring the boot process with a terminal app, the only output is:
PSH KERNEL VERSION: b0182727
..WR: 20104000
SCU IPC: 0x800000d0 0xfffce92c
PSH miaHOB version: TNG..B0..VVBD..0000000c
microkernel. built 23:15:13. Apr 24 2014.
******* PSH loader *******
PCM page cache size = 192 KB
Cache Constraint = 0 Pages
Arming IPC driver ..
Adding page store pool ..
PagestoreAddr(IMR Start Address) = 0x04899000
pageStoreSize(IMR Size) = 0x00080000
**** Ready to receive application ****
After this, the Edison loops every X amount of time. If I disconnect and reconnect power, the exact result is obtained.
I have also tried to boot from OsX / Debian / Linux with no results.
When running the flashall.sh scripts, the device is never found.
I have tried everything I have found online, and have run out of ideas...
I am now sure the Edison has a physical problem. I tried with a new one and was able to boot it up without any trouble. I already talked to the company I bought it from and they will be doing a refund.
Related
I'm developing a script that permits to connect to the internet through a Mediatek MT7612U wifi adapter (Alfa AWUS036ACM) and making some connection tests using speedtest-cli, iperf3 ...
My script is running under OpenWrt linux system. I installed Openwrt in a raspberry PI4 Model B. I plugged to the raspberry two wifi adapter (Alfa AWUS036ACM with Mediatek MT7612U chipset).
The script is running permenantly, and making periodically some connection Tests. After a period of time I lost the connection.
When I checked the system log I found this error reported by the kernel:
kern.err kernel: [ 1929.020945] mt76x2u 2-1:1.0: error: mt76x02u_mcu_wait_resp failed with -110
The issue disappear when I reboot the system. But I need to fix it without rebooting.
I tried to reset the usb device with ioctl USBDEVFS_RESET but that caused the lost of corresponding network interfaces,
I tried also to poweroff/poweron the usb device with commands like that:
echo disabled > /sys/bus/usb/devices/usb2/power/wakeup
echo enabled > /sys/bus/usb/devices/usb2/power/wakeup
but the issue is not fixed
I tried also to unbind/bind the usb device
echo '2-1' > /sys/bus/usb/drivers/usb/unbind
echo '2-1' > /sys/bus/usb/drivers/usb/bind
and the issue is not fixed also
Has someone an idea why I got this blocker issue. Is there an idea to fix or bypass it without the need to reboot the system.
I've also been getting this exact issue. I've also been using the Alfa AWUS036ACM.
I've tried unplugging the adapter and that resets it, then after putting it into monitor mode again it works for a short while before failing with the issue OP has again. I'm using a Raspberry Pi 3b
I'm trying to enable USB 2.0 Host on an AST2500 based board. I'm using the latest obmc-phosphor-image from GitHub which contains Linux 5.10.30. EHCI seems to start in QEMU but fails on real HW. I enabled ehci0 (or ehci1) in the device tree, added the necessary drivers to Linux and I get the following error message during boot-up:
ehci-platform 1e6a1000.usb: USB 2.0, controller refused to start: -110
I investigated EHCI registers a bit and found that when ehci_run() function in ehci-hcd.c would start EHCI (by setting CMD_RUN bit) it remains halted, HCHalted bit in USBSTS register remains 1.
I also saw that the frame index register starts to count when CMD_RUN is asserted. Clock and reset bits in SCU registers are set properly by pinctrl and clk drivers.
Contents of the periodic list buffer and the asynchronous QH buffer seem to be OK. But EHCI still doesn't start.
Strangely UHCI (USB 1.1 host) seems to work properly.
Did maybe somebody manage to get EHCI working on real AST2500 or similar hardware?
Thanks for any advice.
I possess the USRP X310 with a Basic TX daughterboard installed. My plan is to use it via 10GbE together with LabView with a Win10 host machine.
I have connected the SDR with an Ethernet cable using Port 0 and the included SFP adapter to my host PC's (1GbE) ethernet interface for network testing purposes. The ethernet adapter is configured to use the static IP 192.168.10.1. Furthermore I have installed the UHD (uhd_3.15.0.0-release_Winx64_VS2017.exe). However when the device is connected and powered on, I can neither ping 198.168.10.2 nor detect it running the uhd_find_devices.exe. I have also started the NI-USRP Configuration Utility which I recently updated but it was not able to detect the SDR either. I do observe that none of the LEDs on the back is illuminated (especially not the Port 0 ethernet).
How can I get it working?
If you've worked with other usrps (I have a few), then you'll find the X310 to be somewhat different, to the lower models.
Anyway, there are different fpga loads / images, which corrospond to whether you are trying to connect via a 1G or 10G module.
"The PCIe interface is always available regardless of what FPGA image is loaded. Ettus ships two FPGA image variants, the HG or HGS image which has one 1 GigE interfaces and one 10 GigE interfaces, and the XG image which has two 10 GigE interfaces.
So you need to be sure you have the right image to connect to it via 1GE... or I expect it won't work, as it seems to be.
HTH's.
I have a new HP Pavilion running Fedora 20. Wired internet is full speed, but there are several problems with my WiFi connection.
When running best, the speed is a fraction of wired speed.
The connection frequently cuts out completely.
When loading a webpage, errors are thrown
I would like to run 5G connection, but it does not look like it's available
Below I have listed the WiFi driver specs and an error log. Any help is greatly appreciated.
WiFi Driver Specs:
lspci
08:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
Error Log:
journalctl -lf
Aug 19 19:13:03 localhost.localdomain gnome-session[2072]: [3025:3325:0819/191303:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates
Aug 19 19:19:24 localhost.localdomain kernel: perf interrupt took too long (2528 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[3025:3132:0819/192237:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer
Aug 19 19:22:37 localhost.localdomain gnome-session[2072]: [3025:3132:0819/192237:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
Looks like this is a known bug.
The only way round it at the moment is to download and compile the new version of the Realtek driver:
git clone http://github.com/lwfinger/rtlwifi_new.git
cd rtlwifi_new
make
sudo modprobe -rv rtl8188ee
sudo make install
sudo modprobe -v rtl8188ee
The last three commands can be run either with sudo as above, or else by running su after the first three, and then typing in the root password to become root.
(You'll need to experiment to see what dependencies you need installed to build the driver.)
The very low wifi speed compared to wired is entirely normal for wifi, particularly under less than ideal circumstances. Suggest you install wavemon and watch how the signal, signal to noise, retries, etc. slow wifi down. Using wifi can slow you're whole network down by keeping the router busy resending bad packets. it's not unusual for half the packets to have to be sent repeatedly (sometimes several times). Wifi is convenient for some things, but will fundamentally always be slower than a wired connection. This situation has been severely aggravated by the increasing use of wifi, and worse still channel bonding to increase speed which basically can try to tie up all the wifi channels, and then there are those fools who think more power is the answer but that only increases the interference from the high powered transmitter (also illegal). Sadly the attempts to make wifi better have actually created more problems, which the industry now realizes. Also note that you're likely to have more problems on the 5ghz channels as the signal is higher frequency and more sensitive to it's enviroment. Having said that if most of the people around you aren't using the higher band it may work very nicely, until everyone starts overloading those channels as well.
I'd like to write a Ruby program for OSX that communicates via USB with my Arduino.
I am going to use the serialport gem for that purpose.
I found a sample code that says:
port_str = "/dev/ttyUSB0" #may be different for you
How can I scan and find the Arduino, and know to what port I should connect to automatically?
(I have OSX)
Thanks!
This can be tricky to do in a general way, because Arduino devices appear as USB serial ports, making it hard to distinguish between Arduino and non-Arduino ports.
The brute-force approach is: enumerate the USB serial devices, open() each in turn, and see if your firmware boot header is sent on the other end. On OSX, the USB serial devices are at /dev/tty.*, but that may change with future OS updates. This method works, but can be slow and timing sensitive. I've found that a startup delay on the Arduino before sending a header helps, as well as a simple "hello, are you there?" command the host can use to bang for signs of life.
Also, you can save the last port found so that subsequent app launches try that port first.
A variant: if your app asks the user to plug in the Arduino at startup, you can list the USB ports in /dev, wait for user to confirm it's plugged in, and list the ports again. Any newly appearing device is likely your Arduino.
At the next level, you could look at the USB Vendor and Product IDs (VID & PID). However, these IDs are all over the map in Arduino-land. They differ by model, version, revision, Chinese clones, and the various Arduino-compatible devices. See this writeup at Adafruit.
If you're just trying to make things work with a very narrow hardware set (e.g. the one Arduino on your bench), you can use this OSX command to see the USB device details:
system_profiler SPUSBDataType
With my system, I get:
...
USB Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x7fff000027c9
PCI Revision ID: 0x7fff00000002
PCI Vendor ID: 0x7fff00008086
Bus Number: 0x3d
Communication Device:
Product ID: 0x0043
Vendor ID: 0x2341
Version: 0.01
Serial Number: 75331313133351800000
Speed: Up to 12 Mb/sec
Manufacturer: Arduino (www.arduino.cc)
Location ID: 0x3d100000 / 2
Current Available (mA): 500
Current Required (mA): 100
The location ID (0x3d100000 / 2) seems to match up with the device name: /dev/cu.usbmodem3d11
See this question for running command line commands from within a Ruby script.