What environment must be used to program it?
The document Node Location Solution Kit With TTN V1.0.pdf tells a lot, very detailed how to setup ttn & cayenne, but nothing about the programming environment.
In github the explanaitions are rather slimm.
Thanks for a helpful hint
OK. I managed to install all neede parts, changed Commissioning and the Region and could successfully compile it.
At the end I miss a j-link programmer with the appropriate connector to upload the program
RAK811 tracker board compilation
documentation http://www.rakwireless.com/en/download/RAK811%20TrackerBoard/HardWare%20Design
http://www.rakwireless.com/en/download/RAK811%20TrackerBoard/Software%20Development
download and install http://www.coocox.org/software/coide.php --> CoIDE-V2Beta-20170510.exe
https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads --> gcc-arm-none-eabi-7-2017-q4-major-win32.exe
https://github.com/RAKWireless/RAK811_BreakBoard
change Commissioning.h
change configuration remove Defined Symbol --> AS923
add --> REGION_EU868 (not only EU868)
build F7
Program Size:
text data bss dec hex filename
78492 1644 6736 86872 15358 RAK811Breakboard_classA.elf
Does somone know how to connect RAK811 Tracker to J-Link Adapter (Segger)?
I didn’t find much information about.
My proposal:
JLINK <-> RAK811
1 VRef <-> VCC? (JLINK is 5V, but RAK811 is 3.3V?!?)
9 TCK/SWCLK <-> SWD_CLK
6 GND <-> GND
7 TMS/SWDIO <-> JTMS/SWDIO
15 RESET <-> NRST
13 TDO/SWO <-> ???
I would suggest contacting the guys at RAK directly.
They helped me with a binary that I just had to load onto my RAK811 WisNode board to do soe some local coverage mapping (the code was direved from their tracking s/w).
You don‘t need a J-Link debugger. You can compile the sources to get a .bin file. Then you need a piece of software you can download from ST to flash the board. The documentation of RAK explains this.
with what piece of hardware?
the documentation say to use j-tag.
not shure if „flash demonstrator“ could be used.
if you have other experiance, please document your procedure here. thanks
In CoIDE go to the Configuration window and there to Output.
Make sure that Create BIN File is checked.
When using the flash loader demonstrator make sure you change the file type to .bin in the file selection dialog box when you locate the .bin file from your compile run.
Does anyone have tried to use a BME280 sensor with the RAK811 trackerboard? How? Any example code? The example code provided by RAK (that doesn’t support it) is a bit strange to understand, is that me or not? Any better examples from your experiments with it?
thanks for your suggestions and tipps.
I could manage to compile and upload via "demonstrator"
That’s the good news
The bad is that
The demonstrator recognizes the board only after several disconnections/connections of the usb.
(I’ll get a j-tag borrowed. probably that runs better)
The software (classA) has a define which must be deleted in DEVICE_EUI !!! #define IEEE_OUI 0x60, 0xC5, 0xA8 #define LORAWAN_DEVICE_EUI { IEEE_OUI, 0x00, 0x47, … } <-- DELETE IEEE_OUI
The board sends all 60 to 90 sec messages on SF12
first after join on port 0 a message with 12 bytes, but in the device it shows [not provided]
19:10:21 867.7 lora 4/5 SF12BW125 1155.10 dev addr:26012D67 payload size:12 bytes --> 19:10:20 0 0 dev id:rak811_tracker_01 payload:[not provided]
physical pyload from the gateway 40672D012680 09007A35729A first 6 bytes are always the same
then messages on port 4 , 2 , 4 with 21 bytes
19:13:09 868.5 lora 4/5 SF12BW125 1482.83 dev addr:26012D67 payload size:21 bytes --> 19:13:09 3 4 dev id:rak811_tracker_01 payload:0267010E0403019B
cycling through port 0 , x , x , x , 0 , x , x , x , 0 , …
any idea what the meaning of the message on port 0 could be?