![]() ![]() The SDK kernel works fine on the board using nand as a primary boot #Mtk resources edit driver> In addition, can I have a check whether you have run valid nand driver > on your platform before? Can you do a full device erase operation at > first, then use this V4 for your test? Tried that just now, the driver defaults to 12 and problem remains #Mtk resources edit how to> Because the ecc-size and ecc-strength settings are optional, so if you > are not sure how to set them, you can remove the setting from DT file. the problem with theĭocumentation is that FDM is unknown to me. I tried 12 aswell and it also gives an error. > You can get the setting as mtk-nand DT Documentation description. > For this nand, its ecc-strength is max 12 bit per 1024B for our > controller. > Your ecc-strength setting is wrong, because your nand device's OOB size > is not enough to store 24 bit ecc parity data. What i dont understand just yet is, do these erros i am seeing mean theĮcc core is not brought up properly or do they come from the dts The ecc-strength can be calculated and the amount of dts properties can To me it is ambigous what FDM actually is. When i see errors during probe, the core will have received 2 ecc irqs mtk-ecc 1100e000.ecc: decoder timeout - interrupt did not mtk-nand 1100d000.nfi: eccsize 1024 eccstrength 24 nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, nand: device found, Manufacturer ID: 0xef, Chip ID: 0xda Hexdump on the device node will then throw ecc timeouts. values of 16 and below will probe without error but If i set the ecc-strength above 16 it will give irq errors during bootĪs shown below. X-Spam-Checker-Version: SpamAssassin 3.3.1 () on RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY ![]() To: mtd: mediatek: driver for MTK Smart Device Gen1 NAND X-Gm-Message-State: AOPr4FViSy2lY6bS88rNN5hvi6efIl9VuCYeB6oRdBv/gWVcFV4ZYTda8RXDk2DRje5/kF1P ![]() ZdAFGU+ca54w/uZ50lAGvfYc2A9UVb6s5affB/te8Th1VCCEvoJ9Wv/YoPZQp4brG+aXĠ/KYVYfbpFbzWSKboq8aZ8gKcf1V5M1QfX0QFrLjw41sQ7WBpE4o8TPt2Kl7Zrp1pgeC TnSp9M5sQB5BO595S8W0gQqS7KnzfoThMEPOTA5+hthV8Zr69jjsRIaDoOtNBK9IfdMxĠI+0Yq22eqh95IRU+GJWlG04bM/12BZGni5/DRQoLiV0ctMZjtfBB1PoIK3bPajXVc0F H=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-toī=jbxA4G0061oj7+8u3B+T4V2PkvaYcmQPGUCNJSz3Jrwamws5NtX+uVFtn1Xl3f7sYI X-Google-DKIM-Signature: v=1 a=rsa-sha256 c=relaxed/relaxed VY+9dgoy6+OyerFh0EgjNQ6NmD28661FJrFTuCd92FPKKdYNXtR圓3xvTjZLwrLZ8m2l H=from:to:cc:subject:date:message-id:in-reply-to:references īh=tWJTMyLr7yFCPR//XqllBHNmdCBRr4SWy/1U5Jb5VtM= ī=Cszky5IHsRPqLIFWCwDgYv9BVEeMsucrTyxIGyjAMq54o9X8lcxNRfbW8SHiSj3IPV Received: by with SMTP id r184so47480643qkc.1ĭKIM-Signature: v=1 a=rsa-sha256 c=relaxed/relaxed d= s=google Received: from ()īy with esmtps (Exim 4.80.1 #2 (Red Hat Received: from localhost ( helo=)īy with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) Received: from (localhost )īy (Postfix) with ESMTP id A372A20212 X-Original-To: from ( )īy (Postfix) with ESMTP id 18329BF29F ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |