RIOT-OS
thingy91 proto
Contribution description
I am working on compatiblilty of Thingy91board for RiotOS. This is a prototyp of it where alot of parts are missing.
Testing procedure
use <RIOTBASE> as the path to the
root of RIOT. You should replace that with your own path.
1. Go to the application directory:
$ cd <RIOTBASE>/tests/shell
2. Build and flash the application for your board:
$ BOARD=thingy91 make all flash
3. Now we have to start the JLink debugger manually (this is the part
that is not currently working for some reason). For this you need the
JLink software, which we installed yesterday (don't forget to replace
<RIOTBASE> with your path):
$ JLinkExe -nogui 1 -exitonerror 1 -device "NRF9160_XXAA" -speed
"2000" -if "SWD" -jtagconf -1,-1 -commandfile
<RIOTBASE>/dist/tools/jlink/term.seg
4. On ANOTHER terminal, execute pyterm on the correct port:
$ <RIOTBASE>/dist/tools/pyterm/pyterm -ts 19021
You should see RIOT shell's prompt ('>'), if not try pressing Enter.
Issues/PRs references
@Quanterm There is still some remaining issues pointed out. There is also some missing new line at end of files + some trailing whitespaces that must be removed.
I think @Quanterm come in mostly for Hack'n'ACK which was skipped this month. Next month hopefully...
I think last we spoke we wanted to cleanup the board/cpu includes:
./dist/tools/buildsystem_sanity_check/check.sh x
Command output:
Invalid build system patterns found by ./dist/tools/buildsystem_sanity_check/check.sh:
Makefiles files from cpu must not be included by the board anymore:
boards/thingy91/Makefile.features:16:#include $(RIOTCPU)/nrf9160/Makefile.features
Makefiles files from cpu must not be included by the board anymore:
boards/thingy91/Makefile.include:16:include $(RIOTCPU)/nrf9160/Makefile.include
These includes should either be a boards/common/* if included from the board or a cpu/* if included from the cpu. I think the issue was to do with the cpu not being set correctly but we can pick it up from there next hacknack