DevHeads IoT Integration Server•14mo ago

I know that maybe for rapid development I will use it but i am still learning

segfaultdev.elfOP•11/8/24, 7:33 PM

so for now I will give it a try

segfaultdev.elfOP•11/8/24, 7:34 PM

https://github.com/undefined2001/FreeRTOS-BlackPill.git

GitHub

GitHub - undefined2001/FreeRTOS-BlackPill: This repository contains...

This repository contains the necessary code to operate a STM32F411CEU6 - undefined2001/FreeRTOS-BlackPill

segfaultdev.elfOP•11/8/24, 7:34 PM

in case if you want to share some of your words in this

Ssegfaultdev.elf I know that maybe for rapid development I will use it but i am still learning

Techist•11/8/24, 7:34 PM

Perfect.

Been awhile I worked on freeRTOS though.

TTechist Perfect. Been awhile I worked on freeRTOS though.

segfaultdev.elfOP•11/8/24, 7:38 PM

even though it doesn’t make much sense but I love to write my own driver

Ssegfaultdev.elf https://github.com/undefined2001/FreeRTOS-BlackPill.git

Techist•11/8/24, 7:38 PM

I see you are using uart for logging purpose right?

Where are you calling the uart write function?

_io_puts private function?

segfaultdev.elfOP•11/8/24, 7:39 PM

you can check debug.c

segfaultdev.elfOP•11/8/24, 7:39 PM

for better information

segfaultdev.elfOP•11/8/24, 7:40 PM

_io_puts is called by a system call which is _write that is kinda overhead to what i exactly need

segfaultdev.elfOP•11/8/24, 7:40 PM

so I just wrote my printk to do the job

Ssegfaultdev.elf even though it doesn’t make much sense but I love to write my own driver

Techist•11/8/24, 7:41 PM

Yeah, I get you.

That's fine.

You should define your mask values and bit positions as macros too.

You'd have a hard time understanding that code in months to come.

TTechist Yeah, I get you. That's fine. You should define your mask values and bit posit...

segfaultdev.elfOP•11/8/24, 7:41 PM

in which file?

segfaultdev.elfOP•11/8/24, 7:42 PM

in main.c those configurations I did it was for rapid testing

segfaultdev.elfOP•11/8/24, 7:42 PM

I usually use CMSIS so those are already defined

Ssegfaultdev.elf _io_puts is called by a system call which is _write that is kinda overhead to wh...

Techist•11/8/24, 7:43 PM

Placing your uart write in io_puts should be able to achieve the same result.

I think so.

TTechist Placing your uart write in io_puts should be able to achieve the same result. ...

segfaultdev.elfOP•11/8/24, 7:43 PM

yeah no doubt about it

Ssegfaultdev.elf I usually use CMSIS so those are already defined

Techist•11/8/24, 7:43 PM

Ooh, makes much sense.

Yeah, I saw you your cmsis lib.

Techist•11/8/24, 7:43 PM

Kudos

segfaultdev.elfOP•11/8/24, 7:44 PM

but printf is invoking some system call which is more resource hungry so I get the functionality I need but a bit less cost

segfaultdev.elfOP•11/8/24, 7:45 PM

in the past I used to call my uart_send_char inside _io_putchar

segfaultdev.elfOP•11/8/24, 7:46 PM

also printf might use a larger buffer to store data i only made my buffer for 100 characters

segfaultdev.elfOP•11/8/24, 7:46 PM

which is more than enough to logging data

Techist•11/8/24, 7:48 PM

Well, the printk implementation is fine anyways.

It's justiable if you are using it for learning purpose.

segfaultdev.elfOP•11/8/24, 7:48 PM

also i thought it would better rather than sending character by character in each _io_putchar call

segfaultdev.elfOP•11/8/24, 7:49 PM

I am sending it as a buffer

segfaultdev.elfOP•11/8/24, 7:49 PM

:excusemewhat:

Ssegfaultdev.elf I am sending it as a buffer

Techist•11/8/24, 7:50 PM

Your uart driver still sends it per character, lol.

TTechist Your uart driver still sends it per character, lol.

segfaultdev.elfOP•11/8/24, 7:50 PM

yeah but in a single function call

Techist•11/8/24, 7:50 PM

So it doesn't make much difference, lol

TTechist So it doesn't make much difference, lol

segfaultdev.elfOP•11/8/24, 7:50 PM

maybe but it was one of my initial thoughts

Ssegfaultdev.elf maybe but it was one of my initial thoughts

Techist•11/8/24, 7:51 PM

It's entirely fine.

I need to join a meeting now.
I'm glad to know that you fixed your bugs.

Happy building.

TTechist It's entirely fine. I need to join a meeting now. I'm glad to know that you fix...

segfaultdev.elfOP•11/8/24, 7:52 PM

thanks man

segfaultdev.elfOP•11/8/24, 7:52 PM

it feels really good to share the process with someone

segfaultdev.elfOP•11/8/24, 7:52 PM

:salute:

Ssegfaultdev.elf :salute:

Techist•11/8/24, 7:53 PM

Accur4te•11/9/24, 5:37 AM

hey guys any one has any idea about connecting hc - 06 bluetooth module to esp32 bluethooth

AAccur4te hey guys any one has any idea about connecting hc - 06 bluetooth module to esp32...

Umesh Lokhande•11/9/24, 6:00 AM

Just use basic client-server architecture. Let's say for example hc-06 module to be used as a client and by programming ESP32's bluetooth to act as a server so as to establish communication

UUmesh Lokhande Just use basic client-server architecture. Let's say for example hc-06 module to...

Accur4te•11/9/24, 6:01 AM

i tried various codes for the same , all of them are not working . i am unable to get any good article/page for it , can you suggest any article for the same

AAccur4te hey guys any one has any idea about connecting hc - 06 bluetooth module to esp32...

Marvin•11/9/24, 6:01 AM

If you are asking about physical connection, H6-06 can be connected via UART.

MMarvin If you are asking about physical connection, H6-06 can be connected via UART.

Accur4te•11/9/24, 6:02 AM

i am asking about the bluetooth pairing

AAccur4te i am asking about the bluetooth pairing

Marvee Amasi•11/9/24, 6:14 AM

Have u try setting up the ESP32 in Bluetooth Serial mode with

BluetoothSerial

BluetoothSerial

HC 06 uses Bluetooth Classic, so code it to handle pairing as a Bluetooth Serial device, not BLE. Once you ve gotten the ESP32 set as a server, make sure its discoverable and try pairing with AT commands from HC 06

Marvee Amasi•11/9/24, 6:15 AM

Then check this ESP32's

BluetoothSerial

BluetoothSerial

library examples cus they re a good starting point for Classic Bluetooth pairing

AAccur4te i am asking about the bluetooth pairing

Renuel Roberts•11/9/24, 7:20 AM

If u want to directly use the

ESP32’s

ESP32’s

built-in Bluetooth functionality, you can opt for

Classic Bluetooth

Classic Bluetooth

Bluetooth Low Energy

Bluetooth Low Energy

(BLE) depending on your project.

Classic Bluetooth

Classic Bluetooth

is great for continuous data exchange, while

BLE

BLE

is optimized for low-power, intermittent communication.

#include "BluetoothSerial.h"
#include <BLEDevice.h>
#include <BLEServer.h>

BluetoothSerial ESP_BT;  // Classic Bluetooth object

void setup() {
  Serial.begin(115200);

  // Classic Bluetooth setup
  ESP_BT.begin("ESP32_BT_Device");  // Name the device
  Serial.println("Classic Bluetooth Device is Ready to Pair");

  // BLE setup
  BLEDevice::init("ESP32_BLE_Server");  // Name the BLE server
  BLEServer *pServer = BLEDevice::createServer();
  Serial.println("BLE Server is Running");
}

void loop() {
  // Handle Classic Bluetooth data
  if (ESP_BT.available()) {
    char received = ESP_BT.read();
    Serial.write(received);  // Echo received data
  }

  // BLE logic can be added here as needed for advanced configurations
}

#include "BluetoothSerial.h"
#include <BLEDevice.h>
#include <BLEServer.h>

BluetoothSerial ESP_BT;  // Classic Bluetooth object

void setup() {
  Serial.begin(115200);

  // Classic Bluetooth setup
  ESP_BT.begin("ESP32_BT_Device");  // Name the device
  Serial.println("Classic Bluetooth Device is Ready to Pair");

  // BLE setup
  BLEDevice::init("ESP32_BLE_Server");  // Name the BLE server
  BLEServer *pServer = BLEDevice::createServer();
  Serial.println("BLE Server is Running");
}

void loop() {
  // Handle Classic Bluetooth data
  if (ESP_BT.available()) {
    char received = ESP_BT.read();
    Serial.write(received);  // Echo received data
  }

  // BLE logic can be added here as needed for advanced configurations
}

segfaultdev.elfOP•11/9/24, 7:57 AM

segfaultdev.elfOP•11/9/24, 7:57 AM

I am getting this whenever I reset my MCU

segfaultdev.elfOP•11/9/24, 7:58 AM

which introduce a garbage character to my serial monitor

segfaultdev.elfOP•11/9/24, 7:58 AM

is it normal and how to prevent it?

Renuel Roberts•11/9/24, 8:09 AM

@Undefined A spurious serial data transmission occurring when your microcontroller (

MCU

MCU

) resets is kinda common which leads to a garbage character appearing on your serial monitor. it's usually caused by

UART Line Behavior During Reset

UART Line Behavior During Reset

Baud Rate Instability

Baud Rate Instability

and electrical noise to resolve this u should use a capacitor on d reset pin to reduce noise and signal instability and also ensure

UART

UART

transmissions are only enabled after full initialization, Implement pull-up/pull-down resistors on UART lines to prevent them from floating and apply logic to ignore or filter unexpected characters during startup.

RRenuel Roberts @Undefined A spurious serial data transmission occurring when your microcontroll...

segfaultdev.elfOP•11/9/24, 8:13 AM

got it

#include "BluetoothSerial.h" #include <BLEDevice.h> #include <BLEServer.h> BluetoothSerial ESP_BT; // Classic Bluetooth object void setup() { Serial.begin(115200); // Classic Bluetooth setup ESP_BT.begin("ESP32_BT_Device"); // Name the device Serial.println("Classic Bluetooth Device is Ready to Pair"); // BLE setup BLEDevice::init("ESP32_BLE_Server"); // Name the BLE server BLEServer *pServer = BLEDevice::createServer(); Serial.println("BLE Server is Running"); } void loop() { // Handle Classic Bluetooth data if (ESP_BT.available()) { char received = ESP_BT.read(); Serial.write(received); // Echo received data } // BLE logic can be added here as needed for advanced configurations }

I know that maybe for rapid development I will use it but i am still learning

Similar Threads

Similar Threads

Similar Threads