Orange LED flashing slow fast means what?

I've googled and read datasheets and can't find a thing about the orange LED (DL2).

It's flashing 4 times slow then 4 times fast. (and repeating)

Anyone know exactly what this means? Is it just "I've crashed!"?

Is this in your car or bicycle or where?
Paul

Well it says [Hardware][Nano Family][Nano RP2040 Connect] right under the post title. So, I'm guessing it's on a Nano RP2040 Connect?

what did you do to cause this?

Do you know how many people post under the wrong category each day? Lots!
Paul

Ran some code that's not working.

I was only asking about the orange slow/fast blinking. Just need confirmation that it just means crashed, and wondering if there are other patterns meaning different things.

But perhaps I should expand...

I'm trying to get a ST7735 based display working on RP2040 Connect using TFT_eSPI.

#define TFT_MOSI PIN_SPI_MOSI
#define TFT_SCLK PIN_SPI_SCK
#define TFT_CS   10  // Chip select control pin D10
#define TFT_DC   8  // Data Command control pin
#define TFT_RST  19  // Reset pin 

#include <Arduino.h>
#include <TFT_eSPI.h>

TFT_eSPI tft = TFT_eSPI();

void setup() {
    Serial.begin(9600);
    while (!Serial);
    Serial.println("Setup Start...");
    //Serial.flush();

    tft.init();
    Serial.println("tft.init();");
    tft.setRotation(3);
    tft.setTextSize(1);
    tft.setTextColor(TFT_YELLOW);
    tft.drawString("hello world", 0, 0);
}

void loop() {
// write your code here
}

It's crashing in arduino::MbedSPI::beginTransaction (from TFT_eSPI::init), specifically on a call to mbed::SPI::format for which I can't find the source, think it's in a compiled lib?

void arduino::MbedSPI::beginTransaction(SPISettings settings) {
    if (settings != this->settings) {
        Serial.println(dev != nullptr);                                        // my diagnostics
        Serial.println(dev->obj != nullptr);                               // my diagnostics
        dev->obj->format(8, settings.getDataMode());             // CRASH here
        Serial.println("GOT HERE3");                                        // my diagnostics
        dev->obj->frequency(settings.getClockFreq());
        this->settings = settings;
    }
}

Welcome to the forum.

It is likely in the libmbed.a file. See

C:\Users\UserName\AppData\Local\Arduino15\packages\arduino\hardware\mbed_nano\2.4.1\variants\NANO_RP2040_CONNECT\libs

Yes, its the mbedOS crashed signal. I am not aware of other patterns. You can get some more information from the hardware serial port when mbedOS crashes.

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.