Welcome, Guest

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
A20 / Re: Armbian 3.4.113 & 4.14.15 SPI / I2C / NAND / SATA Updated 29.1.2018
« Last post by igorpec on September 19, 2018, 09:33:01 PM »
Major update: https://docs.armbian.com/Release_Changelog/

apt update & apt upgrade
12
TERES DIY Laptop / Re: Armbian Stretch and Bionic with 4.18.y
« Last post by igorpec on September 19, 2018, 07:11:30 PM »
A few numbers which are also not very representative. 4.18.y does not have DVFS yet so CPU stays clocked at 800Mhz.

Armbian: http://ix.io/1n1K
Stock: http://ix.io/1n2D

>No brightness control


At least this should be possible to implement soon, the rest I haven't researched yet.

>I've tried suspending the laptop from Xfce

Suspend works only when the lid is closed.
13
MSP430 / MSP430 5419 HELP!!! Tiny2
« Last post by Mav_2014 on September 19, 2018, 06:07:55 PM »
Hi everyone

I'm having problems with the above, it will read the device no problem but when I try to erase it or program it the olimex software keeps saying "check calibration" . I'm running the 2.0.0.7 firmware,  can anyone help?

Many thanks all

Tony
14
A20 / A20-OLinuXino-MICRO: SATA interface hardware failure?
« Last post by Nate on September 19, 2018, 03:54:00 PM »
I have an A20-OLinuXino-MICRO for almost a year.  Early on I set it up to use Devuan (a Debian derivative) with a 60 GB SATA SSD as the root file system.  After being up for several months with no apparent issues, I had to reboot it two weeks ago and saw the kernel reporting ATA errors of the form:

Code: [Select]
Sep  5 21:47:20 wxbox kernel: [    1.690757] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  5 21:47:20 wxbox kernel: [    1.696591] ata1.00: configured for UDMA/133
Sep  5 21:47:20 wxbox kernel: [    1.701894] ata1: EH complete
Sep  5 21:47:20 wxbox kernel: [    1.719428] ata1.00: exception Emask 0x12 SAct 0x8000000 SErr 0xa80500 action 0x6 frozen
Sep  5 21:47:20 wxbox kernel: [    1.724798] ata1.00: irq_stat 0x08000000, interface fatal error
Sep  5 21:47:20 wxbox kernel: [    1.730118] ata1: SError: { UnrecovData Proto 10B8B BadCRC LinkSeq }
Sep  5 21:47:20 wxbox kernel: [    1.735406] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    1.740701] ata1.00: cmd 60/08:d8:88:0a:74/00:00:07:00:00/40 tag 27 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    1.740701]          res 40/00:dc:88:0a:74/00:00:07:00:00/40 Emask 0x12 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    1.751312] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    1.756516] ata1: hard resetting link
Sep  5 21:47:20 wxbox kernel: [    1.839341] usb 4-1: new full-speed USB device number 2 using ohci-platform
Sep  5 21:47:20 wxbox kernel: [    2.090743] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  5 21:47:20 wxbox kernel: [    2.096356] ata1.00: configured for UDMA/133
Sep  5 21:47:20 wxbox kernel: [    2.101624] ata1: EH complete
Sep  5 21:47:20 wxbox kernel: [    2.107771]  sda: sda1 sda2
Sep  5 21:47:20 wxbox kernel: [    2.114784] sd 0:0:0:0: [sda] Attached SCSI disk
Sep  5 21:47:20 wxbox kernel: [    2.114835] sda: detected capacity change from 0 to 64023257088
Sep  5 21:47:20 wxbox kernel: [    2.125389] usb 4-1: New USB device found, idVendor=10c4, idProduct=ea60
Sep  5 21:47:20 wxbox kernel: [    2.130530] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep  5 21:47:20 wxbox kernel: [    2.135500] usb 4-1: Product: CP2102 USB to UART Bridge Controller
Sep  5 21:47:20 wxbox kernel: [    2.139401] EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities
Sep  5 21:47:20 wxbox kernel: [    2.141003] EXT4-fs (sda2): couldn't mount as ext2 due to feature incompatibilities
Sep  5 21:47:20 wxbox kernel: [    2.150405] usb 4-1: Manufacturer: Silicon Labs
Sep  5 21:47:20 wxbox kernel: [    2.155324] usb 4-1: SerialNumber: 0001
Sep  5 21:47:20 wxbox kernel: [    2.160734] ata1.00: exception Emask 0x12 SAct 0x20 SErr 0xa80500 action 0x6 frozen
Sep  5 21:47:20 wxbox kernel: [    2.165879] ata1.00: irq_stat 0x08000000, interface fatal error
Sep  5 21:47:20 wxbox kernel: [    2.171045] ata1: SError: { UnrecovData Proto 10B8B BadCRC LinkSeq }
Sep  5 21:47:20 wxbox kernel: [    2.176075] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.180977] ata1.00: cmd 60/08:28:00:08:40/00:00:00:00:00/40 tag 5 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.180977]          res 40/00:2c:00:08:40/00:00:00:00:00/40 Emask 0x12 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.190784] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.195644] ata1: hard resetting link
Sep  5 21:47:20 wxbox kernel: [    2.530742] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  5 21:47:20 wxbox kernel: [    2.536122] ata1.00: configured for UDMA/133
Sep  5 21:47:20 wxbox kernel: [    2.541074] ata1: EH complete
Sep  5 21:47:20 wxbox kernel: [    2.559447] ata1: limiting SATA link speed to 1.5 Gbps
Sep  5 21:47:20 wxbox kernel: [    2.564406] ata1.00: exception Emask 0x10 SAct 0x7e000007 SErr 0x280100 action 0x6 frozen
Sep  5 21:47:20 wxbox kernel: [    2.569376] ata1.00: irq_stat 0x08000000, interface fatal error
Sep  5 21:47:20 wxbox kernel: [    2.574208] ata1: SError: { UnrecovData 10B8B BadCRC }
Sep  5 21:47:20 wxbox kernel: [    2.579077] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.584023] ata1.00: cmd 60/08:00:40:29:40/00:00:00:00:00/40 tag 0 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.584023]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.594105] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.599080] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.604128] ata1.00: cmd 60/08:08:48:29:40/00:00:00:00:00/40 tag 1 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.604128]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.614213] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.619175] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.624146] ata1.00: cmd 60/08:10:50:29:40/00:00:00:00:00/40 tag 2 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.624146]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.634182] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.639101] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.644099] ata1.00: cmd 60/08:c8:10:29:40/00:00:00:00:00/40 tag 25 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.644099]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.654121] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.659061] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.664066] ata1.00: cmd 60/08:d0:18:29:40/00:00:00:00:00/40 tag 26 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.664066]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.674337] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.679447] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.684524] ata1.00: cmd 60/08:d8:20:29:40/00:00:00:00:00/40 tag 27 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.684524]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.694831] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.699897] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.705067] ata1.00: cmd 60/08:e0:28:29:40/00:00:00:00:00/40 tag 28 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.705067]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.715498] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.720657] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.725792] ata1.00: cmd 60/08:e8:30:29:40/00:00:00:00:00/40 tag 29 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.725792]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.736190] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.741329] ata1.00: failed command: READ FPDMA QUEUED
Sep  5 21:47:20 wxbox kernel: [    2.746482] ata1.00: cmd 60/08:f0:38:29:40/00:00:00:00:00/40 tag 30 ncq dma 4096 in
Sep  5 21:47:20 wxbox kernel: [    2.746482]          res 40/00:0c:48:29:40/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Sep  5 21:47:20 wxbox kernel: [    2.756894] ata1.00: status: { DRDY }
Sep  5 21:47:20 wxbox kernel: [    2.762106] ata1: hard resetting link
Sep  5 21:47:20 wxbox kernel: [    3.090736] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep  5 21:47:20 wxbox kernel: [    3.096400] ata1.00: configured for UDMA/133


After some more errors from sd 0:0:0:0:, things settled down for a few days and then it seemed to fail completely on the evening of Sep 8.

Suspecting the SSD I temporarily installed it in my laptop, booted from a CD and ran fsck on it.  All seemed fine.  I tried the SSD with the MICRO again and saw a steady stream of ATA errors with just the drive attached but the rootfs on /dev/mmcblk0p2 and not even attempting to mount any partition on the SSD.  I had another small spinner drive laying around so I set it up like the SSD and tried it and still saw the ATA errors.  I tried a different SATA cable with both drives and still received errors.

I have since opted to run the root system on /dev/mmcblk0p2 and have connected the SSD with a SATA to USB adapter I had laying around with partitions on the SSD mounted as /home and /var (where the majority of disk write operations take place in my application) from /etc/fstab.  All is working well for over a week without errors.

I am concerned that the ATA hardware is failing on my MICRO.  Should I seek a replacement or is there something else can could cause the failure messages?  While my present setup using the SSD connected via USB is working, it's not as clean as I'd like as the SSD is outside the case and both USB ports are constantly in use.  I am also concerned that there might be additional hardware failures in the future should this failure indeed be hardware related.

15
A20 / Re: Battery level on Lime2
« Last post by LubOlimex on September 19, 2018, 07:13:01 AM »
Maybe the OpenWRT doesn't support it out-of-the-box. Worth asking the OpenWRT community. If it doesn't support it then you can access the AXP209 power management chip via I2C and read it, but this might be a little bit more complicated (but challenge will not stop you I hope). Refer to the AXP209 documentation about the registers.

Another option is to switch to our Debian or Armbian images, or use Armbian directly, these support battery level in the kernel and you can find the level with a command or even application.
16
A20 / Re: Battery level on Lime2
« Last post by andru97 on September 18, 2018, 05:16:18 PM »

Howdy,

I began utilizing Lime2 as of late. I am utilizing OpenWRT with Lime2. I am driving the board utilizing LiPo battery. I couldn't figure out how to discover the battery level. I utilize SSH to speak with the board. Is there any content or approach to discover the battery level through SSH. Help, if you don't mind.
 ;D ;D


Regards,


Download Terrarium TV for PC.

Install terrarium tv app on roku
17
PIC / Re: PIC-WEB help Request
« Last post by imran on September 18, 2018, 01:14:52 PM »
I tried the above steps but unable to operate 16 outputs. when I clicked on the 11th-15th led. second led output triggers. I dont know why 
18
PIC / Re: ALBUS Lathe CNC Conversion
« Last post by kyrk.5 on September 18, 2018, 11:00:43 AM »
Hi,

very nice :)

For the SW did you checked GRBL? I have managed to port it to a PIC32 and removed a lot of uggly blocking call from it. Now it behaves very nicely and can be used with other nicely written SW part :)

19
SHIELDS / Re: Olimexino Nano GSM not reacting to UART
« Last post by LubOlimex on September 18, 2018, 08:49:39 AM »
You can use either resistors in series or a dedicated level-shifter chip.

Shows us the part of your schematic with the main chip and the UART, maybe it is something obvious.
20
SHIELDS / Re: Olimexino Nano GSM not reacting to UART
« Last post by derchris on September 17, 2018, 07:51:58 PM »
Thanks for the quick reply  :)

One of these is USB. One of the 4p connectors is UART, the other is USB. Is there a chance that you used the USB connector instead of the serial one? I've done it before so it should be possible to mix those.

Nope, I've used the right ones... it works with Olimexino Nano using the same ports.
But I noticed that the Olimexino Nano has 3.3V TTL voltage and maybe that's why there are resistors populated for RX/TX. Since our board has a logic high of 2.8V I could imagine that - because of the resistors - it's too low to be recognized as logical high. I've tried to remove them but broke my board (already ordered a new one). Never did that, so please excuse the question: would it be possible to add a pull-up resistor to our RX/TX to shift it back up to 3.3V so we can use the Nano GSM without tinkering?


> Edit: Something to add is, that it works nicely with the Olimexino MCU. Our TTL logic is 3.3V, might this be the problem?

Which Olimexino? Olimexino-NANO?

yes, correct
Pages: 1 [2] 3 4 ... 10