Does not work on ESP32 Paxcounter LoRa32 T3 V1.6.1

Question

Does not work on ESP32 Paxcounter LoRa32 T3 V1.6.1

SmurfettesBrother opened this issue 2 years ago · comments

The board came with firmware preinstalled. I compiled and flashed my customized version. Now the board hangs in a loop. I think this is a display problem. I'm using the latest version from github. Can someone help?

Thank you

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)<\r><\n> configsip: 188777542, SPIWP:0xee<\r><\n> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00<\r><\n> mode:DIO, clock div:2<\r><\n> load:0x3fff0018,len:4<\r><\n> load:0x3fff001c,len:1044<\r><\n> load:0x40078000,len:10124<\r><\n> load:0x40080400,len:5828<\r><\n> entry 0x400806a8<\r><\n> [I][configmanager.cpp:105] loadConfig(): Loading device configuration from NVRAM...<\r><\n> [I][configmanager.cpp:131] loadConfig(): Runtime configuration v3.0.3 loaded<\r><\n> [I][main.cpp:134] setup(): Starting paxcounter_dab7695c v3.0.3 (runmode=0 / restarts=6)<\r><\n> [I][main.cpp:150] setup(): This is ESP32 chip with 2 CPU cores, WiFi/BT/BLE, silicon revision 1, 4MB embedded Flash<\r><\n> [I][main.cpp:152] setup(): Internal Total heap 258760, internal Free Heap 232876<\r><\n> [I][main.cpp:158] setup(): ChipRevision 1, Cpu Freq 240, SDK Version v3.3.5-1-g85c43024c<\r><\n> [I][main.cpp:160] setup(): Flash Size 4194304, Flash Speed 40000000<\r><\n> [I][main.cpp:162] setup(): Wifi/BT software coexist version 1.2.0<\r><\n> [I][main.cpp:166] setup(): IBM LMIC version 1.6.1468577746<\r><\n> [I][main.cpp:171] setup(): Arduino LMIC version 4.1.1.0<\r><\n> [I][lorawan.cpp:173] printKey(): DevEUI: 4C7525C36274FEFF<\r><\n> [I][lorawan.cpp:173] printKey(): AppEUI: 70B3D50000000000<\r><\n> [I][lorawan.cpp:173] printKey(): AppKey: 00000000000000000000000000000000<\r><\n> [I][i2c.cpp:46] i2c_scan(): Starting I2C bus scan...<\r><\n> [I][i2c.cpp:77] i2c_scan(): Device found at 0x3C, type = Unknown<\r><\n> [I][i2c.cpp:80] i2c_scan(): 1 I2C device(s) found<\r><\n> [E][display.cpp:69] dp_setup(): FAILURE in src/display.cpp:69<\r><\n> /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:4826 (xTaskNotify)- assert failed!<\r><\n> abort() was called at PC 0x400954d4 on core 1

Verkehrsrot · Answer 1 · Sun Feb 27 2022 18:48:18 GMT+0800 (China Standard Time)

which board did you select in paxcounter.ini?

Verkehrsrot · Answer 2 · Sun Feb 27 2022 20:22:10 GMT+0800 (China Standard Time)

Note: your log shows that v3.0.3 is installed on the board. This is not the current version (3.2.0), but should work anyway.

SmurfettesBrother · Answer 3 · Tue Mar 01 2022 22:28:18 GMT+0800 (China Standard Time)

Strange, I got the repository with git clone...
Now, I got the zip file, but it still doesn't work. Now, I can't compile anymore. The error "src/i2c.cpp:15:30: error: 'class TwoWire' has no member named 'end'" comes up. No matter which board I choose.

The first time I tried different boards:
heltec.h
heltecv2.h
heltecv21.h
ttgov1.h
ttgov2.h
ttgov21old.h
ttgov21new.h

On my Heltec board this works without any problems

Verkehrsrot · Answer 4 · Wed Mar 02 2022 00:54:34 GMT+0800 (China Standard Time)

Please check your toolchain, this issue looks like you're using outdated libraries.
Wire.cpp

Verkehrsrot · Answer 5 · Wed Mar 02 2022 15:39:35 GMT+0800 (China Standard Time)

Checked & fixed.
You were right, there was a change in i2c.cpp in preparation for Arduino-Espressif 2.x, but master branch is still on 1.0.6.
It should compile now.

Thorsten Zoerner · Answer 6 · Mon Apr 11 2022 09:23:02 GMT+0800 (China Standard Time)

Was was the trick that made issue 1 solved? (so not the i2c.cpp) but the display.cpp error message. I get the same and I think I've got the latest code (same device here - Lora32 T3):

03:18:22.268 > [    42][I][configmanager.cpp:98] loadConfig(): Loading device configuration from NVRAM...
03:18:22.279 > [    44][I][configmanager.cpp:124] loadConfig(): Runtime configuration v3.2.1 loaded
03:18:22.290 > [    48][I][main.cpp:115] setup(): Starting paxcounter_cfc65d02 v3.2.1 (runmode=0 / restarts=46)
03:18:22.301 > [    55][I][main.cpp:116] setup(): code build date: 1649643373
03:18:22.301 > [    61][I][main.cpp:132] setup(): This is ESP32 chip with 2 CPU cores, WiFi/BT/BLE, silicon revision 3, 4MB external Flash
03:18:22.312 > [    72][I][main.cpp:134] setup(): Internal Total heap 225124, internal Free Heap 197132
03:18:22.323 > [    79][I][main.cpp:140] setup(): ChipRevision 3, Cpu Freq 240, SDK Version v4.4-367-gc29343eb94
03:18:22.334 > [    88][I][main.cpp:142] setup(): Flash Size 4194304, Flash Speed 40000000
03:18:22.334 > [    95][I][main.cpp:144] setup(): Wifi/BT software coexist version 1.2.0
03:18:22.345 > [   101][I][main.cpp:148] setup(): IBM LMIC version 1.6.1468577746
03:18:22.345 > [   107][I][main.cpp:153] setup(): Arduino LMIC version 4.1.1.0
03:18:22.374 > [   133][I][i2c.cpp:49] i2c_scan(): Starting I2C bus scan...
03:18:22.557 > [   321][I][i2c.cpp:77] i2c_scan(): Device found at 0x34, type = AXP192
03:18:22.558 > [   321][I][i2c.cpp:80] i2c_scan(): 1 I2C device(s) found
03:18:22.564 > [   321][E][Wire.cpp:159] begin(): Bus already started in Master Mode.
03:18:23.565 > [  1329][E][display.cpp:69] dp_setup(): FAILURE in src/display.cpp:69

tried with different board configs too (as @SmurfettesBrother did).

Verkehrsrot · Answer 7 · Mon Apr 11 2022 13:29:51 GMT+0800 (China Standard Time)

Your log shows board has AXP192 chip, so probably is a T-Beam, not T3. Sure you're using the right .hal file?

Thorsten Zoerner · Answer 8 · Tue Apr 12 2022 06:05:43 GMT+0800 (China Standard Time)

Sure you're using the right .hal file?

Ups... sorry! - I was googling - checking, trying, reading ... and I think I missed one big thing: clean before build & monitor- However the display.cpp error misleaded my focus.

Krzysztof Bednarczyk · Answer 9 · Tue Apr 26 2022 02:48:11 GMT+0800 (China Standard Time)

Also having this same issue:

20:31:12.088 > ets Jun  8 2016 00:22:57
20:31:12.088 > 
20:31:12.088 > rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
20:31:12.088 > configsip: 188777542, SPIWP:0xee
20:31:12.088 > clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
20:31:12.088 > mode:DIO, clock div:2
20:31:12.088 > load:0x3fff0018,len:4
20:31:12.088 > load:0x3fff001c,len:1044
20:31:12.088 > load:0x40078000,len:10124
20:31:12.088 > load:0x40080400,len:5828
20:31:12.088 > entry 0x400806a8
20:31:12.450 > [I][configmanager.cpp:98] loadConfig(): Loading device configuration from NVRAM...
20:31:12.461 > [I][configmanager.cpp:124] loadConfig(): Runtime configuration v3.2.0 loaded
20:31:12.466 > [I][main.cpp:120] setup(): Starting paxcounter_1c5fc883 v3.2.0 (runmode=0 / restarts=8)
20:31:12.472 > [I][main.cpp:121] setup(): code build date: 1650915012
20:31:12.477 > [I][main.cpp:137] setup(): This is ESP32 chip with 2 CPU cores, WiFi/BT/BLE, silicon revision 1, 4MB embedded Flash
20:31:12.488 > [I][main.cpp:139] setup(): Internal Total heap 253368, internal Free Heap 222920
20:31:12.494 > [I][main.cpp:145] setup(): ChipRevision 1, Cpu Freq 240, SDK Version v3.3.5-1-g85c43024c
20:31:12.505 > [I][main.cpp:147] setup(): Flash Size 4194304, Flash Speed 40000000
20:31:12.510 > [I][main.cpp:149] setup(): Wifi/BT software coexist version 1.2.0
20:31:12.516 > [I][main.cpp:153] setup(): IBM LMIC version 1.6.1468577746
20:31:12.522 > [I][main.cpp:158] setup(): Arduino LMIC version 4.1.1.0
20:31:12.527 > [I][lorawan.cpp:173] printKey(): AppEUI: **removed**
20:31:12.533 > [I][lorawan.cpp:173] printKey(): DevEUI: **removed**
20:31:12.538 > [I][lorawan.cpp:173] printKey(): AppKey: **removed**
20:31:12.544 > [I][i2c.cpp:46] i2c_scan(): Starting I2C bus scan...
20:31:12.655 > [I][i2c.cpp:77] i2c_scan(): Device found at 0x3C, type = Unknown
20:31:12.666 > [I][i2c.cpp:80] i2c_scan(): 1 I2C device(s) found
20:31:12.666 > [E][display.cpp:69] dp_setup(): FAILURE in src/display.cpp:69
20:31:12.672 > /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:4826 (xTaskNotify)- assert failed!
20:31:12.688 > abort() was called at PC 0x400955c0 on core 1
20:31:12.688 > 
20:31:12.688 > ELF file SHA256: 0000000000000000
20:31:12.694 > 
20:31:12.694 > Backtrace: 0x40091cd0:0x3ffd02a0 0x40091f4d:0x3ffd02c0 0x400955c0:0x3ffd02e0 0x400d3e97:0x3ffd0300 0x400d3407:0x3ffd0320 0x400d35fa:0x3ffd0350 0x400d51f3:0x3ffd03a0 0x400ed446:0x3ffd0480 0x40092f5e:0x3ffd04a0
20:31:12.880 >   #0  0x40091cd0:0x3ffd02a0 in invoke_abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/panic.c:715
20:31:12.880 >   #1  0x40091f4d:0x3ffd02c0 in abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/panic.c:715
20:31:12.880 >   #2  0x400955c0:0x3ffd02e0 in xTaskNotify at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:4826 (discriminator 1)
20:31:12.880 >   #3  0x400d3e97:0x3ffd0300 in mask_user_IRQ() at src/irqhandler.cpp:114
20:31:12.880 >   #4  0x400d3407:0x3ffd0320 in dp_setup(int) at src/display.cpp:707
20:31:12.880 >   #5  0x400d35fa:0x3ffd0350 in dp_init(bool) at src/display.cpp:707
20:31:12.880 >   #6  0x400d51f3:0x3ffd03a0 in setup() at src/main.cpp:196
20:31:12.880 >   #7  0x400ed446:0x3ffd0480 in loopTask(void*) at /Users/noname/.platformio/packages/framework-arduinoespressif32/cores/esp32/main.cpp:18
20:31:12.880 >   #8  0x40092f5e:0x3ffd04a0 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)
20:31:12.880 >

My board is TTGO LoRa32 V2.1

And platformio.ini setup is

;
; Please visit documentation for the other options and examples
; http://docs.platformio.org/page/projectconf.html


; ---> SELECT THE TARGET PLATFORM HERE! <---
[board]
;halfile = generic.h
;halfile = ebox.h
;halfile = eboxtube.h
;halfile = ecopower.h
;halfile = heltec.h
;halfile = heltecv2.h
;halfile = heltecv21.h
;halfile = ttgov1.h
;halfile = ttgov2.h
;halfile = ttgov21old.h
halfile = ttgov21new.h
;halfile = ttgofox.h
;halfile = ttgobeam.h
;halfile = ttgobeam10.h
;halfile = ttgotdisplay.h
;halfile = ttgotwristband.h
;halfile = fipy.h
;halfile = lopy.h
;halfile = lopy4.h
;halfile = lolin32litelora.h
;halfile = lolin32lora.h
;halfile = lolin32lite.h
;halfile = wemos32oled.h
;halfile = wemos32matrix.h
;halfile = octopus32.h
;halfile = tinypico.h
;halfile = tinypicomatrix.h
;halfile = m5core.h
;halfile = m5fire.h
;halfile = olimexpoeiso.h

[platformio]
; upload firmware to board with usb cable
default_envs = usb
; upload firmware to a paxexpress repository
;default_envs = ota
; use upstream version of arduino-espressif32 framework
;default_envs = dev
description = Paxcounter is a device for metering passenger flows in realtime. It counts how many mobile devices are around.

[common]
; for release_version use max. 10 chars total, use any decimal format like "a.b.c"
release_version = 3.2.0
; DEBUG LEVEL: For production run set to 0, otherwise device will leak RAM while running!
; 0=None, 1=Error, 2=Warn, 3=Info, 4=Debug, 5=Verbose
debug_level = 3
extra_scripts = pre:build.py
otakeyfile = ota.conf
lorakeyfile = loraconf.h
lmicconfigfile = lmic_config.h
platform_espressif32 = espressif32@3.5.0
monitor_speed = 115200
upload_speed = 115200 ; set by build.py and taken from hal file
display_library = ; set by build.py and taken from hal file
lib_deps_lora =
    mcci-catena/MCCI LoRaWAN LMIC library @ ^4.1.1
lib_deps_display =
    bitbank2/OneBitDisplay @ ^1.11.0
    ricmoo/QRCode @ ^0.0.1
    bodmer/TFT_eSPI @ ^2.3.84
lib_deps_ledmatrix =
    seeed-studio/Ultrathin_LED_Matrix @ ^1.0.0
lib_deps_rgbled =
    https://github.com/RoboticsBrno/SmartLeds.git
lib_deps_gps =
    mikalhart/TinyGPSPlus @ ^1.0.2
lib_deps_sensors =
    adafruit/Adafruit Unified Sensor @ ^1.1.4
    adafruit/Adafruit BME280 Library @ ^2.2.1
    adafruit/Adafruit BMP085 Library @ ^1.2.0
    boschsensortec/BSEC Software Library @ 1.6.1480
    https://github.com/cyberman54/sds-dust-sensors-arduino-library.git
lib_deps_basic =
    https://github.com/dbSuS/libpax.git @ ^1.0.0
    https://github.com/SukkoPera/Arduino-Rokkit-Hash.git
    bblanchon/ArduinoJson @ ^6
    makuna/RTC @ ^2.3.5
    spacehuhn/SimpleButton 
    lewisxhe/AXP202X_Library @ ^1.1.3
    256dpi/MQTT @ ^2.4.8
lib_deps_all =
    ${common.lib_deps_basic}
    ${common.lib_deps_lora}
    ${common.lib_deps_display}
    ${common.lib_deps_rgbled}
    ${common.lib_deps_gps}
    ${common.lib_deps_sensors}
    ${common.lib_deps_ledmatrix}
build_flags_basic =
    -include "src/hal/${board.halfile}"
    -include "src/paxcounter.conf"
    '-DCORE_DEBUG_LEVEL=${common.debug_level}'
    '-DLOG_LOCAL_LEVEL=${common.debug_level}'
    '-DPROGVERSION="${common.release_version}"'
    '-Wno-unknown-pragmas'
    '-Wno-unused-variable'
    '-D LIBPAX_WIFI'
    '-D LIBPAX_BLE'
    '-D LIBPAX_ARDUINO'
build_flags_all =
    ${common.build_flags_basic}
    -mfix-esp32-psram-cache-issue

[env]
framework = arduino
;board = esp32dev
board = ttgo-lora32-v21
board_build.mcu = esp32
board_build.partitions = min_spiffs.csv
upload_speed = ${common.upload_speed}
upload_port = /dev/cu.wchusbserial54250257671
platform = ${common.platform_espressif32}
lib_deps = ${common.lib_deps_all}
build_flags = ${common.build_flags_all}
upload_protocol = ${common.upload_protocol}
extra_scripts = ${common.extra_scripts}
monitor_speed = ${common.monitor_speed}
monitor_filters = time, esp32_exception_decoder, default

[env:ota]
upload_protocol = custom

[env:usb]
upload_protocol = esptool

[env:dev]
upload_protocol = esptool
build_type = debug
platform = https://github.com/platformio/platform-espressif32.git#feature/arduino-upstream

The issue is on 3.2 release downloaded as zip folder & on master branch too. What are the best way to debug it and find the problem?

Verkehrsrot · Answer 10 · Tue Apr 26 2022 04:15:58 GMT+0800 (China Standard Time)

I can confirm this. I have reproduced this on a TTGO T3 v1.6.1 board, as well as on a completely different board, but with the same display type SSD1306.

The issue is caused by the used display library, and needs to be further tracked down there.
I opened issued there:
bitbank2/OneBitDisplay#29

Verkehrsrot · Answer 11 · Tue Apr 26 2022 04:19:21 GMT+0800 (China Standard Time)

Meanwhile you can try* to upgrade to Arduino 2.x and use the latest version of onebitdisplay library. I had success with this with another board, but not yet with the T3 v1.6.1. Need to be investigated what's going wrong here. Maybe it's an i2c bus related issue.

*) by editing following lines in platformio.ini:

;platform_espressif32 = espressif32@3.5.0
platform_espressif32 = espressif32@4.1.0
...
lib_deps_display = 
...
;bitbank2/OneBitDisplay @ ^1.11.0
https://github.com/bitbank2/OneBitDisplay.git

Krzysztof Bednarczyk · Answer 12 · Tue Apr 26 2022 05:03:54 GMT+0800 (China Standard Time)

I think it can be i2c bus issue or issue with Wire library (but less likely)
I tested master branch of OneBitDisplay, like you purposed, but problem is this same.
So then i decided to downgrade this package to version 1.10 and 1.9.1 - nothing changed - problem still persist.
Before each change of version i clicked "clean all" on VS platform.io plugin , to be sure the library is this same like i defined in config.

Hardware issue i think i can exclude, because stock firmware works well - version 3.0.3

Meanwhile you can try* to upgrade to Arduino 2.x

With this im not sure if i did it correctly, because new version for mac os is separated application, not overwriting older version 1.8. So in this case i removed completely 1.8 version from the system and kept 2.0 rc

Let me know how else i can help, so i will try to give support.

Verkehrsrot · Answer 13 · Tue Apr 26 2022 05:21:51 GMT+0800 (China Standard Time)

To wrap up, it seems two different phenomens can be seen:

display is not detected by onebitdisplay lib, causing assert failure in display.cpp of paxcounter
display is detected and works, but showing only two lines and with wrong text placement

I currently have no idea what's going wrong here.

Verkehrsrot · Answer 14 · Tue Apr 26 2022 22:04:44 GMT+0800 (China Standard Time)

This should now be fixed by this commit

Solution was to force onebitdisplay lib to use Wire for i2c bus, not hardware bitbanging.

Attention: Please apply modifications of platformio_orig.ini to your local platformio.ini before rebuild.

@bordeux @SmurfettesBrother could you please retest and report here? Thanks.

Krzysztof Bednarczyk · Answer 15 · Tue Apr 26 2022 23:49:05 GMT+0800 (China Standard Time)

@cyberman54 checked latest master branch with your changes, but problem still appears.

I will try to debug it by myself - like you said the problem can be with onebit display library or wrong parameters. I will let know about my findings.

Verkehrsrot · Answer 16 · Wed Apr 27 2022 05:19:53 GMT+0800 (China Standard Time)

@bordeux i double checked the patch with three boards (TTGO T3 1.6.1, Olimex PoE, T-Fox) - all with working display. Strange.

Krzysztof Bednarczyk · Answer 17 · Wed Apr 27 2022 05:43:32 GMT+0800 (China Standard Time)

@cyberman54 yeah, that is strange. I still debugging it, i just created simple code bellow, to test OneBitDisplay library.
There are 2 functions:

ssd1306lib - works fine like expected
onebitlib - not working, unable to find display (so this same issue like with pax counter)
Tested with different parameters, with and without i2c address, different speeds and any good results from my side.

How possible is share to me your binary from TTGO T3 1.6.1, without of course lorawan and other credentials? Because it for you it works there are 2 possibilities for me:

the problem is between my chair and my monitor (highly possible)
problem is in TTGO T3 1.6.1 itself - maybe different, cheaper parts.

#include <Arduino.h>
#include <OneBitDisplay.h>
#include <ArduinoLog.h>
#include <Wire.h>
#include <Adafruit_I2CDevice.h>
#include <Adafruit_GFX.h>
#include <Adafruit_SSD1306.h>

#define SDA_PIN 21
#define SCL_PIN 22

#define OLED_ADDR 0x3c

#define FLIP180 0
// don't invert the display
#define INVERT 0
// Bit-Bang the I2C bus
#define USE_HW_I2C 0

#define RESET_PIN -1

#define SCREEN_WIDTH 128 // OLED display width, in pixels
#define SCREEN_HEIGHT 64 // OLED display height, in pixels

void onebitlib()
{
  OBDISP obd;
  Log.verboseln("Start testing using OneBitDisplay library");

  int rc = obdI2CInit(&obd, OLED_128x64, OLED_ADDR, FLIP180, INVERT, 0, SDA_PIN, SCL_PIN, RESET_PIN, 400000L); // use standard I2C bus at 400Khz
  if (rc != OLED_NOT_FOUND)
  {
    Log.verboseln("Oled found!");
    obdFill(&obd, 0, 1);
    obdWriteString(&obd, 0, 0, 0, "OneBitScreen!", FONT_8x8, 0, 1);
  }
  else
  {
    Log.verboseln("Oled NOT found!");
  }
}

void ssd1306lib()
{
  Adafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT, &Wire, RESET_PIN);
  Log.verboseln("Start testing using SSD1306 library");
  if (!display.begin(SSD1306_SWITCHCAPVCC, OLED_ADDR))
  {
    Log.verboseln(F("SSD1306 allocation failed"));
  }
  else
  {
    Log.verboseln("Oled using SSD1306 lib works!");
    display.display();
    display.clearDisplay();
    display.setTextSize(1);            
    display.setTextColor(SSD1306_WHITE); 
    display.setCursor(0, 0);     
    display.cp437(true);
    display.println(F("Lorem ipsum"));
    display.display();
    Log.verboseln("Finished rendering!");
  }
}

void setup()
{
  Serial.begin(9600);
  Log.begin(LOG_LEVEL_VERBOSE, &Serial);
  Log.verboseln("Starting application");
  delay(1000);
  //ssd1306lib();
  onebitlib();
}

void loop() {}

and platform io

[platformio]
default_envs = ttgo-lora32-v21

[env]
lib_deps = 
	andeepmistry/arduino-LoRa @ ^0.8.0
	bitbank2/OneBitDisplay @ ^1.11.0
	thijse/ArduinoLog@^1.1.1
        adafruit/Adafruit SSD1306@^2.5.3
build_flags = 
	-D VERSION=1.2.3
	-D DEBUG=1
lib_deps_builtin = 
	SPI
	Wire
upload_port = /dev/cu.wchusbserial54250257671

[env:ttgo-lora32-v21]
platform = espressif32
board = ttgo-lora32-v21
framework = arduino

Verkehrsrot · Answer 18 · Wed Apr 27 2022 05:54:32 GMT+0800 (China Standard Time)

@bordeux before paxcounter initializes the display, it does a i2c scan with bitbang lib by same author. I made the modification here. Please look in i2c.cpp and add that piece of code to your test code. It made the issue disappearing here, but i yet cannot explain why.

Krzysztof Bednarczyk · Answer 19 · Wed Apr 27 2022 06:19:18 GMT+0800 (China Standard Time)

Just added

void onebitlib()
{
  BBI2C bbi2c;

  memset(&bbi2c, 0, sizeof(bbi2c));
  bbi2c.bWire = 1;
  bbi2c.iSDA = SDA_PIN;
  bbi2c.iSCL = SCL_PIN;
  I2CInit(&bbi2c, 100000L); // Scan at 100KHz low speed
  delay(100);

  OBDISP obd;
  Log.verboseln("Start testing using OneBitDisplay library");

  int rc = obdI2CInit(&obd, OLED_128x64, OLED_ADDR, FLIP180, INVERT, 0, SDA_PIN, SCL_PIN, RESET_PIN, 400000L); // use standard I2C bus at 400Khz
  if (rc != OLED_NOT_FOUND)
  {
    Log.verboseln("Oled found!");
    obdFill(&obd, 0, 1);
    obdWriteString(&obd, 0, 0, 0, "OneBitScreen!", FONT_8x8, 0, 1);
  }
  else
  {
    Log.verboseln("Oled NOT found!");
  }
}

But OneBitDisplay is using own instance of BBI2C, so modifications on i2c scanner part from my opinion should not affect onebitdisplay.
I2C scanner on paxcounter works fine, even before modifications, correctly finding 0x3c device

mietse · Answer 20 · Wed Apr 27 2022 06:46:31 GMT+0800 (China Standard Time)

Change this file and now my display is working.

file: display.cpp

#if (HAS_DISPLAY) == 1 // I2C OLED

int rc = obdI2CInit(&ssoled, OLED_TYPE, OLED_ADDR, MY_DISPLAY_FLIP,
MY_DISPLAY_INVERT, USE_HW_I2C, MY_DISPLAY_SDA,
MY_DISPLAY_SCL, MY_DISPLAY_RST,
OLED_FREQUENCY); // use standard I2C bus at 400Khz
//_ASSERT(rc != OLED_NOT_FOUND); //<< blockout this line >>

// set display buffer
obdSetBackBuffer(&ssoled, displaybuf);
obdSetTextWrap(&ssoled, true);
dp_font = MY_FONT_NORMAL;

Krzysztof Bednarczyk · Answer 21 · Wed Apr 27 2022 06:54:42 GMT+0800 (China Standard Time)

@mietse lol :D Yeah, this works! Funny, OneBit display returning not found status, but it found. Definitely wrong detection on onebitdisplay lib :)

Verkehrsrot · Answer 22 · Wed Apr 27 2022 13:15:39 GMT+0800 (China Standard Time)

of course we can dismiss the assert. But this does not solve the problem. The question is, why is the display not found?

If is was found before, it is evident that some change, either in display lib or wire driver of framework is the root cause, since there were no changes in paxcounter.