From owner-freebsd-arm@freebsd.org Wed Oct 7 08:59:14 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 85EEC429669 for ; Wed, 7 Oct 2020 08:59:14 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4C5pDL26yJz4Z6f for ; Wed, 7 Oct 2020 08:59:14 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 47076429668; Wed, 7 Oct 2020 08:59:14 +0000 (UTC) Delivered-To: arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 46D18429445 for ; Wed, 7 Oct 2020 08:59:14 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C5pDK34fjz4YqW for ; Wed, 7 Oct 2020 08:59:13 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lj1-f182.google.com with SMTP id y16so33459ljk.1 for ; Wed, 07 Oct 2020 01:59:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=6bnp3PVR6BrcAEJYmKR4N3I1MjaofVK8tm7usFZOLnE=; b=APIMZjxhutHODD06zzo3p78b9EdWjzQyN1npPEM+WaIhHZG4fV22KGmUNclfMgBFG3 aU1cdw/Zh1nTp3kMdS0pnUc1W1YWhgviDSCEWTBIuu0YOun1MKmwPn/gstbCnnyVDldb jXSKY5z7SnKM4vLOJQFvbDnlBxIhlK7x8JLSyF/k0o1vO3qd01yQJ8bNX71AK4m7swqT pXgXaGeT8WT14JgayxpWBr1BANVJBW7/lrhW6c08gdgNHlL6/+MWjXxLaOgxYN19MAe7 ra9w4SwKDRWCblswkXE76xFbvCvwZ2r78oxLM343bSDjx7qjE5jKYlB8/caK9Ah4pDWz 8zTQ== X-Gm-Message-State: AOAM531o0jNM1I7FFRjQ3WaQRwfQkQCgGYsXZCQx+k+l94pZTYJ+1KKi d/h5qfwPWKN+oLqDdinOZvwlK8OojHiAiA== X-Google-Smtp-Source: ABdhPJzbprMa4j9dIuVgZ0pkUCXys0z7lpwwZRq7ijCaP7S3f1EqcC9FT4VvC556tWcdH7vVczlOMg== X-Received: by 2002:a2e:89c1:: with SMTP id c1mr875077ljk.385.1602061150571; Wed, 07 Oct 2020 01:59:10 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id b18sm258504ljj.5.2020.10.07.01.59.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 07 Oct 2020 01:59:09 -0700 (PDT) Subject: Re: nanopi/allwinner i2c not working. From: Andriy Gapon To: Daniel Braniss Cc: "freebsd-arm@freebsd.org" References: <234D06ED-C99F-477E-8D95-492979084E7A@cs.huji.ac.il> <7934CE38-DC3F-450A-A131-19A7F88DA9EC@cs.huji.ac.il> <20201006104119.28f2262d47107d41025d193f@bidouilliste.com> <29A34854-E792-48CE-AF0A-E4C605BDFC3B@cs.huji.ac.il> <6416CA90-AB4C-4F8A-BCF4-7C9E5A4F2F8D@cs.huji.ac.il> <0ba109b4-784f-19ed-e52d-a40b75af872c@FreeBSD.org> <7C27FB6C-BF0D-4DAE-99D0-50849D2FBA5E@cs.huji.ac.il> <43a5d626-634c-2cc2-e8a5-ad4326a2d6e2@FreeBSD.org> <77DC054E-07B2-48F8-8051-C2796EE991B2@cs.huji.ac.il> <260839FF-7297-4FDC-82AC-13797938AC29@cs.huji.ac.il> <9FE1F947-4975-411C-91D1-94C43E5495C8@cs.huji.ac.il> <82ac00f2-0463-3861-dd39-9c079978be27@FreeBSD.org> Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= mDMEX1iFDhYJKwYBBAHaRw8BAQdAiu8JG/oLFkVkOAJqJc7Dx5KI/Q6C3SBI20EQm+DXnAu0 HkFuZHJpeSBHYXBvbiA8YXZnQEZyZWVCU0Qub3JnPoiWBBMWCAA+FiEEyCHHZM09l0OE3Ir/ 1A1+Gq8+L1EFAl9YhQ4CGwMFCQeEzgAFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQ1A1+ Gq8+L1Fc0wD/ZjmhHfbCJywZU3aOxXIPjcz73FYEGMvqMCCLAWyLbSABALFL+1ZNrjV3BGjq 889cOYFuboA/Yn3eWezS+tfqYBsGuDgEX1iFDhIKKwYBBAGXVQEFAQEHQL6B20Xi600TrkpG P9fWjl7JtHNxqrHKhX6Kg7kgb4ILAwEIB4h+BBgWCAAmFiEEyCHHZM09l0OE3Ir/1A1+Gq8+ L1EFAl9YhQ4CGwwFCQeEzgAACgkQ1A1+Gq8+L1F3cgEAktp4h+IJUJxL1vn6zMOt//znni/J TanKfQuA8wGXcGkBAKpZJhqMkg+pKk7MGvJhgJ6nCpTZ+rMK6vZVZLUWc3QF Message-ID: <3eeb74a3-47f1-bf23-bd4a-eae9b5f46daf@FreeBSD.org> Date: Wed, 7 Oct 2020 11:59:08 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Firefox/60.0 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <82ac00f2-0463-3861-dd39-9c079978be27@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4C5pDK34fjz4YqW X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of agapon@gmail.com designates 209.85.208.182 as permitted sender) smtp.mailfrom=agapon@gmail.com X-Spamd-Result: default: False [-2.97 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.958]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[avg@FreeBSD.org,agapon@gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[93.72.151.96:received]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[avg@FreeBSD.org,agapon@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.974]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.04)[-1.037]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[arm@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.182:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.182:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Oct 2020 08:59:14 -0000 On 07/10/2020 11:33, Andriy Gapon wrote: > Perhaps the problem is on the device's side? >From here https://www.nxp.com/docs/en/user-guide/141520.pdf ยง 6.2.4 However, it may happen that the PN532 does not acknowledge its own address immediately after having finished a previous exchange. So, perhaps an application level delay is needed? I am not really familiar with the device and its communication protocol details, so maybe I am talking nonsense. -- Andriy Gapon