The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,380 other followers

Archive for the ‘openSuSE’ Category

USB serial converters from FTDI – how to select them and get rid of fake chips

Posted by jpluimers on 2018/06/08

Be sure to read the comments at USB serial converters from FTDI are quite popular – Thomas Mueller (dummzeuch) – Google+ [WayBack] as it tells more about how to set genuine and fake FTDI chips apart (often before buying them, you cannot tell) and how to replace fake ones buy genuine ones.

Getting back to original means de-soldering fake chips, and soldering new genuine chips on the boards.

Fake chips:

  • have limited batches of the same serial (although there are ways to reprogram the serial, see links below)
    • connecting multiple adapters with the same serial causes trouble
  • are mangled by various FTDI drivers (either their PID is reset, or fake-data is inserted in the serial stream)
  • have problems operating at higher data rates

Note that the workarounds for these fake chips mean you cannot use more recent chips.

Links from Thomas’s post and other relevant links on the various kinds of genuine/fake and getting fake ones work again

Fake chips can cause you a lot of headaches – and time – sorting out communication problems: [WayBack] esptool-ck, esp8266, and FTDI Bug Hunting – vilimblog

Two years ago, this shoot-out (with results on github) had a great conclusion:

Buy either an adapter with a genuine FTDI chip, or one of the Silicon Labs CP2102 chips.

The FTDI chip is the only one attaining 3M baud rates.

Overview articles:

SiLabs chips seem to be the only without much trouble:

  • [WayBack] SiLabs CP210x USB Adapters For The Win – vilimblog
  • Review of a Generic USB RS 232/485/TTL Adapter (“Winners” branded) – YouTube:
    • Almost anything with FTDI/Prolific chips that comes from ebay/aliexpress should be assumed to be counterfeit – easy way to test this is to buy 2 and see if their serial numbers match. You don’t really want to waste your time with fake ones, you’ll end up spending more on those if you try to get them for as cheap as possible. Itead sells an adapter for 6.8 USD with genuine FT232RL chips, but they aren’t in as convenient dongle form factor, but might be worth more than your own time replacing fake chips with genuine ones.Although not mentioned here, CH340/1 should generally be avoided, while they work fine for short periods of time, for longer use they seem to be as unreliable as the counterfeit FTDI/Prolific chips on Linux.

      I haven’t seen or recognized a fake CP210x chip yet, so my guess would be that these are generally fine no matter where you get them. One big advantage of those is the integrated voltage 3.3V regulator, which can save some space when rolling your own boards.

FTDI related:

Genuine FTDI seems to be the easiest to find:

Prolific has similar issues, driver v3.4.25.218 still works with fake chips:

–jeroen

Related posts where I mentioned some of the trouble with FTDI chips:

Read the rest of this entry »

Posted in *nix, Development, Hardware Development, Hardware Interfacing, Legacy Ports: COM, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »

Hmm, latest Tumbleweed on Raspberry Pi 3 has an odd thing booting: Ansi termi…

Posted by jpluimers on 2018/05/25

Reminder to self: since the [ArchiveARM Cortex A53 problems are fixed, check out if this is also fixed:

[WayBack] Hmm, latest Tumbleweed on Raspberry Pi 3 has an odd thing booting: Ansi terminal characters aren’t being processed any more. – Jeroen Wiert Pluimers – Google+

Related: Git repository with fixed binaries for Tumbleweed on Raspberry Pi 3 – Bug 1084419 – Glibc update to 2.27 causes segfault during name resolution

–jeroen

–jeroen

Posted in *nix, Development, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, SuSE Linux, Tumbleweed | Leave a Comment »

CoreFreq – A Powerful CPU Monitoring Tool for Linux Systems

Posted by jpluimers on 2018/05/07

I need to check out if it finally got available for OpenSuSE: [WayBackCoreFreq – A Powerful CPU Monitoring Tool for Linux Systems

via:

Read the rest of this entry »

Posted in *nix, *nix-tools, Linux, openSuSE, Power User, ps, SuSE Linux | Leave a Comment »

use `zypper refresh` when this fails: openSUSE Tumbleweed upgrade – openSUSE

Posted by jpluimers on 2018/04/23

A while ago, when upgrading from CPE_NAME="cpe:/o:opensuse:tumbleweed:20170206" to CPE_NAME="cpe:/o:opensuse:tumbleweed:20170213":

aRetrieving: monitoring-tools-1.14.0-4.2.x86_64.rpm ......................................................................................................[error]
File './x86_64/monitoring-tools-1.14.0-4.2.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/server:/monitoring/openSUSE_Tumbleweed/'

What happened is that the local zypper configuration was out of sync with the repository. A zypper refresh solved that.

So I expanded my zypper-twup alias to always include the zypper refresh.

Then I updated the documentation from [old WayBackopenSUSE:Tumbleweed upgrade – openSUSE to [new WayBackopenSUSE:Tumbleweed upgrade – openSUSE.

Note you need an account at https://login.microfocus.com to logon to the various opensuse.org sites to make edits or post messages.

–jeroen

 

Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »

Git repository with fixed binaries for Tumbleweed on Raspberry Pi 3 – Bug 1084419 – Glibc update to 2.27 causes segfault during name resolution

Posted by jpluimers on 2018/04/08

OSC downloads for [archive.is] https://bugzilla.opensuse.org/show_bug.cgi?id=1084812

The binaries provided by Stefan Brüns, together with installation instructions are now in a git repository at [WayBack] wiert.me/public/linux/opensuse/tumbleweed/aarch64 a.k.a. arm64/1084182-fix-osc-binaries · GitLab.

Follow the steps in Applying the fixes on a broken system to at least temporarily get your system to work (a new zypper dist-upgrade might fail, so be careful with that).

–jeroen

Posted in *nix, *nix-tools, Development, DVCS - Distributed Version Control, git, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, Source Code Management, SuSE Linux, Tumbleweed | Leave a Comment »

 
%d bloggers like this: