sp9unb
/
meshtastic-firmware
sforkowany z mirror/meshtastic-firmware
1
0
Forkuj 0
Kod Zgłoszenia Oczekujące zmiany Packages Projekty Wydania Wiki Aktywność
867 Commity
8 Gałęzie
195 Tagi
44 MiB
Wykres commitów

867 Commity (375ae5fe7706e2cd55d515f7ecd2818aa6a15b4d)

Autor SHA1 Wiadomość Data
geeksville a8a5e036f5 turn off serial debug output once we are using the protocol on the stream 2020-06-09 10:35:06 -07:00
geeksville 009f05b61d temp workaround for sleep bug #167 2020-06-09 06:38:09 -07:00
geeksville d8a6f82459 Merge remote-tracking branch 'root/master' into usb 2020-06-08 16:42:45 -07:00
Kevin Hester 185fe8520a
Merge pull request #164 from rradar/patch-1 
Update build-instructions.md to use code tags
 2020-06-08 16:42:31 -07:00
geeksville ce9bac34d6 add a new SERIAL psm state, to ensure device doesn't sleep while 
connected to the phone over USB.

In support of

https://github.com/meshtastic/Meshtastic-Android/issues/38
 2020-06-08 16:37:49 -07:00
Kevin Hester e80673ed15
Merge branch 'master' into patch-1 2020-06-08 16:32:43 -07:00
geeksville bdbaf9c655 remove old BLE api 2020-06-08 16:08:02 -07:00
geeksville 7473a6c27a unify activity detection in PhoneAPI, turn off BLE API while serial API in use 2020-06-08 16:06:59 -07:00
geeksville 71a4cfefd5 bringup WIP 2020-06-08 15:01:55 -07:00
Kevin Hester 4919129bbc
Merge pull request #165 from slavino/patch-1 
Update README.md
 2020-06-08 13:53:12 -07:00
Slavomir Hustaty a02175cec0
Update README.md 
https://www.everythingrf.com/community/lora-frequency-in-europe

The LoRa Alliance has defined two frequency bands for the usage of LoRa technology in Europe. These bands are EU433 from 433.05 to 434.79 MHz and EU863 from 863 to 870 MHz.

EU433 (433.05 to 434.79 MHz)

The end devices in EU433 band operate from 433.05 to 434.79 MHz and use a channel data structure to support at least 16 channels.

and so on...
https://lora-alliance.org/sites/default/files/2018-04/lorawantm_regional_parameters_v1.1rb_-_final.pdf
 2020-06-08 21:34:02 +02:00
rradar 63affdd2e7
Update build-instructions.md to use code tags 
Update build-instructions.md to make (more) use of code tags
 2020-06-08 10:55:03 +01:00
Kevin Hester 351687e5cd
Merge pull request #160 from geeksville/longaddr 
PROTOCOL CHANGE! activate 32 bit nodenums/packetids
 2020-06-07 22:23:31 -07:00
geeksville 739f497bbd Merge branch 'master' into longaddr 2020-06-07 22:16:43 -07:00
geeksville 2d2ed591e9 set num_bits for nodenum and packet id after loading save file 2020-06-07 22:12:06 -07:00
geeksville 871a85d688 force all devices to discard old settings 2020-06-07 17:22:07 -07:00
geeksville a5f05019db fix build instructions 2020-06-06 14:30:15 -07:00
geeksville e124d2094f PROTOCOL CHANGE! activate 32 bit nodenums/packetids 2020-06-06 13:16:36 -07:00
Kevin Hester 5d874cd43b
Merge pull request #159 from geeksville/master 
hotfix release for reboot bug
 2020-06-06 08:48:14 -07:00
geeksville 9f6cdadd3e Merge remote-tracking branch 'root/master' 2020-06-06 08:43:10 -07:00
geeksville 6a3853ef35 0.6.8 2020-06-06 08:33:20 -07:00
geeksville 9ea65c6793 Fix #153 - details below 
Somehow nodenum was getting reset to zero (and saved to flash - which is
bad because it makes the failure permanent).  So I've changed nodenum
selection to occur after we load the saved preferences (and we try to keep
nodenum stable in that case).

I'm puzzled as to how it ever got set to zero (unless there *shudder*
is some errant pointer that clobbered it).  But next week I'm turning
4 byte nodenums back on, which will make this moot - because they
will always be based on macaddr and the current process where nodes
haggle with the mesh to pick a unique one-byte nodenum will be gone.
 2020-06-06 08:30:01 -07:00
geeksville 8d14e97dfa oops - we were not saving radio state 2020-06-06 08:07:21 -07:00
geeksville 1c63a70673 cubecell WIP 2020-06-05 17:30:09 -07:00
geeksville 8022f3b920 Merge branch 'master' into bringup 2020-06-05 16:02:54 -07:00
Kevin Hester 420b7d48d9
Merge pull request #157 from geeksville/master 
update webpage
 2020-06-05 11:38:17 -07:00
geeksville 5915669f6f Merge remote-tracking branch 'root/master' 2020-06-05 11:33:58 -07:00
geeksville 52b01db306 announce beta 2020-06-05 11:33:19 -07:00
Kevin Hester a0d6ecb331
Merge pull request #156 from geeksville/master 
minor
 2020-06-05 11:09:00 -07:00
geeksville 0271b02d50 Merge remote-tracking branch 'root/master' 2020-06-05 11:06:40 -07:00
geeksville 9f61c78c0e doc merge 2020-06-05 11:05:36 -07:00
geeksville 4db176867b WIP - bringup on PPR 2020-06-05 11:00:58 -07:00
geeksville 4b5cfaf9ba changes from bringing up PPR 2020-06-05 11:00:18 -07:00
Kevin Hester c014c1bafe
Merge pull request #155 from geeksville/master 
now in beta
 2020-06-04 11:28:39 -07:00
geeksville 96594516af now in beta 2020-06-04 11:25:06 -07:00
Kevin Hester bed20bf1fa
Merge pull request #151 from geeksville/longaddr 
Longaddr
 2020-06-04 10:41:39 -07:00
geeksville 4e5a445d8b 0.6.7 2020-06-04 10:37:08 -07:00
geeksville 99437d931e fix #153 2020-06-03 16:08:11 -07:00
geeksville 5166717298 confirm randomSeed is set correctly 2020-06-03 14:24:34 -07:00
geeksville 49b5738f4f add min_app_version so apps can warn if they are too old 2020-06-03 13:57:30 -07:00
geeksville c753ea7cd1 don't use a fixed randomSeed. 2020-06-03 13:51:53 -07:00
geeksville 5b1488ddf0 Allow packet and nodenums to be 32 bits long (but don't change yet) 2020-06-03 13:46:31 -07:00
geeksville a34cfb0ee0 Populate metainfo for apps to allow 32 bit node and packet ids 2020-06-03 13:15:45 -07:00
Kevin Hester d8ff605d32
Merge pull request #147 from geeksville/nrf52 
my DSR changes broke acks for flood routing also.  Fix #146
 2020-06-03 12:57:56 -07:00
geeksville 8031c47602 put nrf52 on back burner for a couple of days 2020-06-03 12:55:55 -07:00
geeksville e522e47544 Full DSR WIP 2020-06-03 12:49:36 -07:00
geeksville ed0f79b683 Merge branch 'master' into nrf52 2020-05-27 15:54:44 -07:00
Kevin Hester de1337d351
Merge pull request #148 from geeksville/master 
fixes for @dafeman's board
 2020-05-27 15:52:00 -07:00
geeksville 1b34a0c6d8 Help make sx1262 go for @dafeman 's board. See below for details: 
Hi, I think the problem you were having building for ESP32 was due to
a funny thing.  Notice the #define for INTERRUPT_ATTR.  That macro expands
to IRAM_ATTR - which is a special flag the ESP32 requires for _any_ code
that is going to be called from an ISR.  So that the code is guaranteed
to be in RAM (the ESP32 uses a clever scheme where the FLASH is actually
high speed serial flash and all reads/writes are actually only happening
to a small number of pages in RAM and they have a driver that is constantly
copying blocks they need into that ram.  This essentially how VM works
for desktop computers, but in their case they are paging to FLASH.

But for code that runs in an interrupt handler must _always_ be in RAM
because if you took a 'page fault' for that code being missing in RAM they
can't nicely do their clever VM scheme.

So that's all good.  The problem was - apparently GCC for the ESP32 has a
a bug when that attribute is applied in the class declaration.  So
I moved it out into the cpp file and all seems well now.
 2020-05-27 15:47:59 -07:00
geeksville 313380381b no need for this old debug output 2020-05-27 15:40:47 -07:00