Date: Wed, 7 Oct 2020 11:59:08 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: "freebsd-arm@freebsd.org" <arm@FreeBSD.org> Subject: Re: nanopi/allwinner i2c not working. Message-ID: <3eeb74a3-47f1-bf23-bd4a-eae9b5f46daf@FreeBSD.org> In-Reply-To: <82ac00f2-0463-3861-dd39-9c079978be27@FreeBSD.org> References: <234D06ED-C99F-477E-8D95-492979084E7A@cs.huji.ac.il> <7934CE38-DC3F-450A-A131-19A7F88DA9EC@cs.huji.ac.il> <e1dd71e2-9ee3-380d-7be9-601a3015652c@FreeBSD.org> <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> <ecc5c0cf-3a5f-ef24-8270-3b95354ee7d9@FreeBSD.org> <F36B7EDD-B9A8-4D9B-854E-B54BFE678AB9@cs.huji.ac.il> <43a5d626-634c-2cc2-e8a5-ad4326a2d6e2@FreeBSD.org> <77DC054E-07B2-48F8-8051-C2796EE991B2@cs.huji.ac.il> <ec611752-8c5f-c4e7-18f2-bafd4a34e594@FreeBSD.org> <260839FF-7297-4FDC-82AC-13797938AC29@cs.huji.ac.il> <f926a7c2-e4c4-5cee-69fa-80a53182bd98@FreeBSD.org> <9FE1F947-4975-411C-91D1-94C43E5495C8@cs.huji.ac.il> <FB320D2F-610B-4773-83FD-681270F743AB@cs.huji.ac.il> <82ac00f2-0463-3861-dd39-9c079978be27@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3eeb74a3-47f1-bf23-bd4a-eae9b5f46daf>