From Arduino Ide to Eclipse Sloeber project for ESP32S3

[atomino-max]

I have created a new sketch with the name of the arduino.ino file ad after I copied in the dedicated workspace.

I am ready to be patient, because eclipse ide is very interesting, my project ca be compiled and uploaded to the device with Arduino Ide 1.8.19 , but how you can see from attachment I start from 2 errors from #include and I don't know from where Arduino can catch these file, other question is how I can select the device ESP32 S3.
Thanks in advance for your help.

[jantje]

Please start with the tutorial linked to in this discussion
#1342

[TrippyLighting]

@atomino-max my recommendation would be to stick with it and work through problems! No doubt this can be frustrating! It sometimes takes a while until all libraries are installed and indexed. And warning messages disappear.
The Arduino environment hides a lot of the complexity from a user. The effect is that you might get smaller projects done, but as your projects get more advanced, the Arduino IDE becomes a real hindrance.

I also think you are starting the transition to Sloeber with a project that is too complex. I usually start with a Blinky when upgrading to a new version of ... anything. New microcontroller, new Sloeber update etc.
Then I try to get some output through the Serial console.
Once the Mic is talking, I can move forward with more complex stuff.

Sloeber is much more capable than the Arduino IDE.

[atomino-max]

Thanks for your suggestion, my project is in fact becoming big and for this reason I have looked for an alternative path. I will try to be patient and see if I can find a solution to the errors that Sloeber is showing me.

[atomino-max]

Any suggestion for this problem ::
usage: esptool [-h]
[--chip {auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32s3,esp32c3,esp32c6beta,esp32h2beta1,esp32h2beta2,esp32c2,esp32c6,esp32h2}]
[--port PORT] [--baud BAUD]
[--before {default_reset,usb_reset,no_reset,no_reset_no_sync}]
[--after {hard_reset,soft_reset,no_reset,no_reset_stub}]
[--no-stub] [--trace] [--override-vddsdio [{1.8V,1.9V,OFF}]]
[--connect-attempts CONNECT_ATTEMPTS]
{load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,make_image,elf2image,read_mac,chip_id,flash_id,read_flash_status,write_flash_status,read_flash,verify_flash,erase_flash,erase_region,merge_bin,get_security_info,version}
...

esptool: error: unrecognized arguments: --flash-mode --flash-freq 80m --flash-size 16MB /esp32s3/bin/bootloader_qio_80m.elf
make: *** [all] Error 2

[atomino-max]

I try the example below but it produces 1 error any help ?

/*
Control Addressable RGB LED
By: Nathan Seidle
SparkFun Electronics
Date: January 13, 2024
License: MIT. Please see LICENSE.md for more information.

This example shows how to illuminate the RGB on the SparkFun ESP32 S3 Thing Plus.

Feel like supporting open source hardware?
Buy a board from SparkFun!
SparkFun ESP32-S3 Thing Plus (DEV-24408) https://www.sparkfun.com/products/24408

Select the following in the Arduino IDE:
Board: ESP32S3 Dev Module
USB Mode: Hardware CDC and JTAG
USB CDC on Boot: Enabled
Upload Mode: UART0 / Hardware CDC
PSRAM: QSPI PSRAM
Port: Select the COM port that the device shows up on under device manager
*/

#include <FastLED.h> // http://librarymanager/All#FastLED

#define LED_PIN 48 //Pin 46 on Thing Plus C S3 is connected to WS2812 LED
#define COLOR_ORDER GRB
#define CHIPSET WS2812
#define NUM_LEDS 1

#define BRIGHTNESS 25

CRGB leds[NUM_LEDS];

void setup()
{
Serial.begin(115200);
//while (Serial == false); //Wait for serial monitor to connect before printing anything

FastLED.addLeds<CHIPSET, LED_PIN, COLOR_ORDER>(leds, NUM_LEDS).setCorrection(TypicalLEDStrip);
FastLED.setBrightness(BRIGHTNESS);
}

void loop()
{
leds[0] = CRGB::Red;
FastLED.show();
delay(200);

leds[0] = CRGB::Green;
FastLED.show();
delay(200);

leds[0] = CRGB::Blue;
FastLED.show();
delay(200);

leds[0] = CRGB::Black;
FastLED.show();
delay(100);

leds[0] = CRGB::White;
FastLED.show();
delay(2000);

leds[0] = CRGB::Black;
FastLED.show();
delay(100);
}

[jantje]

@atomino-max
With the sparse information you provide there is so many possibilities that I get a "do not act" response.
To help users to explain what is wrong I provided following information when a issue is created.
Please read it and try to be more verbose and to the point.

Before continuing.
Click on the preview button so the text is more readable and the links work

Before creating a bug report check for existing issues
Make sure you are on the latest and greatest Sloeber version. We do not support older version.
Here is a list of known limitations
Here is a list of common issues
Here is the list of all open issues
Here is a list of issues that have been fixed but are not yet available in a release

---

Describe your environment
Do you use the Sloeber product or plugin?
Sloeber version number
OS: [e.g. windows 10]
The url of the json that you used to download the platform
A image of the project properties arduino showing the board settings

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

provide the name of the board and the platform version you are using.
Provide the json url and a screenshot of project properties->arduino

Expected behavior
A clear and concise description of what you expected to happen.

Data to back up your claim
If applicable, add screenshots, console output and/or logs to help explain your problem.

Additional context
Add any other context about the problem here.