ESP32-C3 - The connected target does not have support for nanoFramework.Hardware.Esp32.Rmt

[tank104]

Hi,
I am using ESP32-C3-DevKitC-02 Development Board, and trying to change the LED light on the board.
From reading it looks this is and addressable” RGB LED.
Googling has shown me that I need to use nanoFramework.Hardware.Esp32.Rmt.

I have shown code below.

However when I deploy this I get error:
[The connected target does not have support for nanoFramework.Hardware.Esp32.Rmt.]

Do I need to flash the board with extra libraries to support these packages? I can't find anything else to flash that indeicates how to make this work?

Any help appreciated - have searched as much as I can for a solution but come up with nothing.

` s_GpioController = new GpioController();
GpioPin led = s_GpioController.OpenPin(8, PinMode.Output);
using (var rmt_transmitter = new TransmitterChannel(8))
{
// transmitter configuration
rmt_transmitter.CarrierEnabled = false;
//rmt_transmitter.isSource80MHz = true;
rmt_transmitter.ClockDivider = 4; // base period 80 MHz / 4 => 20 MHz -> 0.05 us
//rmt_transmitter.IsChannelIdle = true;
//rmt_transmitter.TransmitIdleLevel = false;

    rmt_transmitter.AddCommand(new RmtCommand(100, true, 100, false));
    rmt_transmitter.AddCommand(new RmtCommand(100, true, 100, false));
    rmt_transmitter.AddCommand(new RmtCommand(100, true, 100, false));
    rmt_transmitter.AddCommand(new RmtCommand(100, true, 100, false));
    // create new pulse command for to transmitt
    // IDLE  0.5us  1us       1.5 us           2 us             2.5 us	   IDLE..
    //      |----|        |------------|                |--------------------|
    // -----|    |--------|            |----------------|                    |------
    rmt_transmitter.Send(true);
  }`

[tank104]

I am also getting a similiar issue when trying to use I2s:

The connected target does not have support for System.Device.I2s

[tank104]

Ahh ok thanks - does it typically take long to get added. Or is it something I can do? (very good c# coder, but near zero experience in nano - if so is there a guide?)

I guess I have brought the latest chips :(

[josesimoes]

Really depends on someone tackling those tasks... None of it it's particularly challenging, yet, this is run mostly out of community effort.
As for the coding: I'm afraid these are at the native end of it, meaning C/C++.

Nevertheless, let's not waste your enthusiasm and willing to help! 😄 Can I interest you on one of the open issues? There are numerous ones C# related. Some are labeled as "good first issue" 😉 This could be a smooth way for getting into this.

[MrCSharp22]

Hi @josesimoes
Is there a write up somewhere on how to bring the RMT library to the ESP32 C3 target? I'd like to tackle this but I am not familiar with CMake. So if there is such a doc, it'd be super helpful.

[josesimoes]

@MrCSharp22 there is no such doc. You're better have the compiler gide you through this.
IDF API is usually the same or pretty close between series, so I'm guessing you'll have to just perform some tweaks (if any are required).

[tank104]

@josesimoes just following up on this - is there anywhere I can see what boards have better support?

Is it safe to assume any of these devices have good support for all libraries:
https://docs.nanoframework.net/content/getting-started-guides/where-to-buy-devices.html

Might be easier for me to just buy them, instead of waiting for changes

[Ellerbach]

Is it safe to assume any of these devices have good support for all libraries:

Yes, it is safe but it's just a subset and some suggestions.

You have the more exhaustive list here and here

[tank104]

Thanks but that list doesn’t show which devices have compatibility/support with which nanoframework libraries? I.e i2s

[Ellerbach]

When you click expand, you have the main libraries. Now, you're right, the list is not fully up to date.
In theory RMT is part of the build. And I2S should be on by default as well.

Now, your code is not correct. You must not open the GPIO pin.

[josesimoes]

I2C is set to off for the C3 series, that's why the target is reporting what you're seeing.
I'm adjusting this in nanoframework/nf-interpreter#2691 so you can test if support for I2C is working properly for C3.

[tank104]

If I have understood correctly - then I have made that change (removing all the REG_SET_BIT - and confirm build is working:
nanoframework/nf-interpreter#2692

Are there instructions I can use to take this build output and test it locally with one of the chips? Sorry haven't done it before, and do need some pointers.

[josesimoes]

@tank104 you can download the build artifacts from the pipeline here then use nanoff to flash the ESP32 for testing.

[tank104]

I had a look there but don't seem to be able to download the artifacts, is it a security issue? Pretty sure I can do it fine on my own DevOp repos inthe past

https://dev.azure.com/nanoframework/nf-interpreter/_build/results?buildId=42886&view=artifacts&pathAsName=false&type=publishedArtifacts

[josesimoes]

😯 indeed!! One needs to be authenticated to download artifacts from a PR build. It seems... as I'm alwyas authenticated, I had never spotted this... pretty sure there is a permission for this...
Do you happen to know what it is?

[tank104]

I don’t, but does this help:
https://developercommunity.visualstudio.com/t/permissions-needed-to-download-build-artifacts/578781

[tank104]

I don’t sorry, always been admin on repos so never thought about it Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: José Simões ***@***.***> Sent: Thursday, July 13, 2023 8:55:00 PM To: nanoframework/Home ***@***.***> Cc: Andrew Thomas ***@***.***>; Mention ***@***.***> Subject: Re: [nanoframework/Home] ESP32-C3 - The connected target does not have support for nanoFramework.Hardware.Esp32.Rmt (Discussion #1198) 😯 indeed!! One needs to be authenticated to download artifacts from a PR build. It seems... as I'm alwyas authenticated, I had never spotted this... pretty sure there is a permission for this... Do you happen to know what it is? — Reply to this email directly, view it on GitHub<#1198 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFMCRB64J52BXCWJPBCPYPLXP6ZWJANCNFSM6AAAAAATE4NSI4>. You are receiving this because you were mentioned.Message ID: ***@***.***>