From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17354 invoked by alias); 28 Jan 2014 10:08:02 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 17341 invoked by uid 89); 28 Jan 2014 10:08:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: relay01.alfahosting-server.de Received: from relay01.alfahosting-server.de (HELO relay01.alfahosting-server.de) (109.237.142.236) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 28 Jan 2014 10:07:59 +0000 Received: by relay01.alfahosting-server.de (Postfix, from userid 1001) id BFAC332C05DA; Tue, 28 Jan 2014 11:07:55 +0100 (CET) X-Spam-DCC: : Received: from alfa3017.alfahosting-server.de (alfa3017.alfahosting-server.de [109.237.140.28]) by relay01.alfahosting-server.de (Postfix) with ESMTPS id 2F1E032C05D4 for ; Tue, 28 Jan 2014 11:07:44 +0100 (CET) Received: from itrrrauch (p578a450a.dip0.t-ipconnect.de [87.138.69.10]) by alfa3017.alfahosting-server.de (Postfix) with ESMTPA id 0E69D293413B for ; Tue, 28 Jan 2014 11:07:44 +0100 (CET) From: "Richard Rauch" To: References: <00fc01cf1c09$ec4f7f30$c4ee7d90$@itrgmbh.de> In-Reply-To: <00fc01cf1c09$ec4f7f30$c4ee7d90$@itrgmbh.de> Date: Tue, 28 Jan 2014 10:08:00 -0000 Message-ID: <010101cf1c10$cbbeb040$633c10c0$@itrgmbh.de> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Virus-Checker-Version: clamassassin 1.2.4 with ClamAV 0.97.3/18407/Tue Jan 28 08:32:25 2014 X-IsSubscribed: yes Subject: AW: [ECOS] Accessing SDHC Cards with 8 GB X-SW-Source: 2014-01/txt/msg00032.txt.bz2 Maybe I found an answer (partially) right now. I am always formatting SDCards ny usage of Windows (I have not verified wit= h Linux, because our customers rarely using Linux) I discovered this:=20 when a SD Card less than 8GB is formatted, it is formatted in a more standa= rd way. In this case in first sector there is a valid MBR with a valid partition t= able. When a SD Card has a size >=3D 8GB, it is formatted differently. No MBR is = generated. In Sector 0 there is located already Bootsector with BPB. Unfortunately eCos do not know about this. When mounting the SD Card, it tr= ies to interpret the BPB as MBR. What I do not know right now: Do I have a unique criteria to decide, if fir= st sector needs to be interpreted as MBR or as boot sector already. And, what would be the best position in eCos driver hierarchy, to code such= a decision. Or maybe, somewhere a solution is already available? Thanks again Richard -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss