Date: Thu, 28 Mar 2024 15:00:23 +0000 (UTC) Message-ID: <1537307144.17.1711638023292@1e5f9dfb671a> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16_1014048778.1711638023292" ------=_Part_16_1014048778.1711638023292 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
= David Burnett Workshop went well! L12 didn=E2=80=99t program. 1 of 8 nR= F DKs wouldn=E2=80=99t program. 2 McCoy boards wouldn=E2=80=99t respond but= the workshop wasn=E2=80=99t designed to work with those. Otherwise, studen= ts successfully got RF transmission running and received by OpenMotes.
<= /li>Austin Patel merged code and not sure what was wrong with Fil=E2=80= =99s boards because they appear to work out of the box.
Tengfei Chang verified BSP functio= ns work. Next step is to run the stack.
When transmitting, waiting a while after tx_enable is necessary before c= alling the transmit function.
The interrupt happens if you call it too early but the openmote doesn=E2= =80=99t hear anything.
From p. 77 of Sahar=E2=80=99s thesis (https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-71.p= df) it looks like the necessary delay might be from the TX FIFO being l= oaded.
Need to figure out a way to determine when the FIFO is finished loading = so the waiting isn=E2=80=99t open loop. Current code is 8 ms but Tengfei Chang experimented and 0.5 ms wait = time works.
There is a TX_LOAD_DONE interrupt
workshop is a success
own hardware
4 students
2 students successful; sweep LO, received on the OpenMote
2 students has issues:
one nRF-DK didn=E2=80=99t work (out of 8)
one Sulu (L12) wouldn=E2=80=99t work (Fil Maksimovic took back)
two McCoy, wasn=E2=80=99t able to work