nRF5340 Getting FOTA to work with both app core and net core simultaneously

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Sigurd Hellesvik — Wed, 20 Sep 2023 13:55:25 GMT

[quote user="Nolan_G"]Do public tickets get closed when they are solved? I'm going to have more questions related to this when I try to add my own custom peripherals, so I'll be returning with questions later today. If it's easier for you, I can open another ticket once I run into more problems.[/quote]

They get closed either if I close them, or if you click "Mark as Answer" on an reply.

New topics is best on new tickets, to keep DevZone clean.

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Wed, 20 Sep 2023 07:19:04 GMT

I see! My app showed "UPLOAD COMPLETE" so I was alarmed when I tried uploading something with the wrong signature. However, the device still showed the same BLE name as the former image, so I was confused. That makes sense!

Thanks so much, and thanks for the tips along the way! Do public tickets get closed when they are solved? I'm going to have more questions related to this when I try to add my own custom peripherals, so I'll be returning with questions later today. If it's easier for you, I can open another ticket once I run into more problems.

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Sigurd Hellesvik — Wed, 20 Sep 2023 07:12:15 GMT

[quote user="Nolan_G"]

Also, what happens when I try to upload a firmware image signed with the wrong signature, but I select Confirm Only? The image with the wrong signature should get rejected, right? But then how does it fall back on the correct firmware from before?

Does checking signatures work with Confirm Only?

[/quote]

Yes, checking of signatures always work. MCUboot will check signatures before swapping, and just not swap, leaving the old application in primary slot

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Wed, 20 Sep 2023 07:05:02 GMT

Okay, great!

Does checking signatures work with Confirm Only?

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Sigurd Hellesvik — Wed, 20 Sep 2023 07:00:25 GMT

[quote user="Nolan_G"]for some odd reason, I got my FOTAing to work after randomly changing a few settings.[/quote]

Exiting news!

[quote user="Nolan_G"]Do you know how to only use internal flash? My coworker told me that we don't have an external flash on our real device (non-DK board), so we have to develop without one.[/quote]

See my previous answer:

[quote user="Sigurd Hellesvik"]

We are working on adding it more easily in these PRs:

https://github.com/nrfconnect/sdk-nrf/pull/10060

https://github.com/nrfconnect/sdk-mcuboot/pull/235

If you want to use internal flash for now, I think you can have a look this sample:

peripheral_lbs_dfu(2).zip

[/quote]

[quote user="Nolan_G"]Thanks so much for your help thus far![/quote]

Happy to help!

[quote user="Nolan_G"]Also, I'm no longer using mcuboot.overlay anymore, and I have that excerpt in my main overlay file. Should I have it separate?[/quote]

You can have overlay filed for DTS three places, and here is the difference:

Board files: Will affect both application and child images
Inside project folder, as described in Set Devicetree overlays. For example project/boards/board_name.overlay. This will affect only application
Inside project/child_image/somewhere, as described in Permanent configuration changes to child images. This will affect only the child image (bootloader in your case

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Wed, 20 Sep 2023 06:48:31 GMT

Also, I'm no longer using mcuboot.overlay anymore, and I have that excerpt in my main overlay file. Should I have it separate?

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Wed, 20 Sep 2023 06:47:32 GMT

Hi Sigurd, for some odd reason, I got my FOTAing to work after randomly changing a few settings.

Here are the files I have right now. It may be a fluke, and I have to look more into it.

My overlay file:

// To get started, press Ctrl+Space to bring up the completion menu and view the available nodes.

// You can also use the buttons in the sidebar to perform actions on nodes.
// Actions currently available include:

// * Enabling / disabling the node
// * Adding the bus to a bus
// * Removing the node
// * Connecting ADC channels

// For more help, browse the DeviceTree documentation at https://docs.zephyrproject.org/latest/guides/dts/index.html
// You can also visit the nRF DeviceTree extension documentation at https://nrfconnect.github.io/vscode-nrf-connect/devicetree/nrfdevicetree.html

/ {
    chosen {
        nordic,pm-ext-flash = &mx25r64;
    };
};


/ {
	zephyr,user {
		io-channels = <&adc 0>, <&adc 1>;
	};
};

&pinctrl {
    spi2_default: spi2_default {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK, 1, 15)>,
                <NRF_PSEL(SPIM_MOSI, 0, 30)>,
                <NRF_PSEL(SPIM_MISO, 1, 0)>;
        };
    };

    spi2_sleep: spi2_sleep {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK, 1, 15)>,
                <NRF_PSEL(SPIM_MOSI, 0, 30)>,
                <NRF_PSEL(SPIM_MISO, 1, 0)>;
            low-power-enable;
        };
    };
};

&spi2 {
    compatible = "nordic,nrf-spim";
    status = "okay";
    cs-gpios = <&gpio1 14 1>;
    pinctrl-0 = <&spi2_default>;
    pinctrl-1 = <&spi2_sleep>;
    pinctrl-names = "default", "sleep";
};

&adc {
    #address-cells = <1>;
    #size-cells = <0>;
 
    channel@0 {
        reg = <0>;
        zephyr,gain = "ADC_GAIN_1_6";
        zephyr,reference = "ADC_REF_INTERNAL";
        zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>;
        zephyr,input-positive = <NRF_SAADC_AIN4>;
    };

    channel@1 {
        reg = <1>;
        zephyr,gain = "ADC_GAIN_1_6";
        zephyr,reference = "ADC_REF_INTERNAL";
        zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>;
        zephyr,input-positive = <NRF_SAADC_AIN5>;
    };
 };

My pm_static.yml:

app:
  address: 0x10200
  end_address: 0x66000
  region: flash_primary
  size: 0x55E00
mcuboot:
  address: 0x0
  end_address: 0x10000
  region: flash_primary
  size: 0x10000
mcuboot_pad:
  address: 0x10000
  end_address: 0x10200
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0x10000
  end_address: 0x66000
  orig_span: &id001
  - mcuboot_pad
  - app
  region: flash_primary
  size: 0x56000
  span: *id001
mcuboot_primary_app:
  address: 0x10200
  end_address: 0x66000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x55E00
  span: *id002
mcuboot_secondary:
  address: 0x66000
  end_address: 0xBC000
  size: 0x56000
mcuboot_secondary_1:
  address: 0xBC000
  end_address: 0xFC000
  size: 0x40000
otp:
  address: 0xff8100
  end_address: 0xff83fc
  region: otp
  size: 0x2fc
pcd_sram:
  address: 0x20000000
  end_address: 0x20002000
  region: sram_primary
  size: 0x2000
ram_flash:
  address: 0x40000
  end_address: 0x40000
  region: ram_flash
  size: 0x0
rpmsg_nrf53_sram:
  address: 0x20070000
  end_address: 0x20080000
  placement:
    before:
    - end
  region: sram_primary
  size: 0x10000
settings_storage:
  address: 0xFC000
  end_address: 0x100000
  region: flash_primary
  size: 0x4000
sram_primary:
  address: 0x20002000
  end_address: 0x20070000
  region: sram_primary
  size: 0x6e000
mcuboot_primary_1:
  address: 0x0
  size: 0x40000
  device: flash_ctrl
  region: ram_flash

My prj.conf:

# Enable Bootloader
CONFIG_BOOTLOADER_MCUBOOT=y

# Enable SMP Server
CONFIG_MCUMGR=y
CONFIG_BASE64=y
CONFIG_MCUMGR_TRANSPORT_UART=y
CONFIG_MCUMGR_GRP_IMG=y

# Enable BLE transfer
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="Test SMP Server"
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP=y
CONFIG_MCUBOOT_IMAGE_VERSION="2.3.0+0"
CONFIG_NRF53_UPGRADE_NETWORK_CORE=y
CONFIG_UPDATEABLE_IMAGE_NUMBER=2
CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS=y


CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

# configure peripherals
CONFIG_NRFX_TWIM0=y
CONFIG_NRFX_TWIM1=y
CONFIG_I2C=y
CONFIG_NRFX_QSPI=n
CONFIG_SPI=y
CONFIG_SPI_EXTENDED_MODES=y
CONFIG_NRFX_SPIM2=y
CONFIG_NRFX_SPIM3=y
CONFIG_NRFX_SPIM4=y
CONFIG_NRFX_TIMER0=y
CONFIG_NRFX_TIMER1=y
CONFIG_NRFX_TIMER2=y
CONFIG_NRFX_PWM0=y

CONFIG_SCHED_DUMB=y
CONFIG_SCHED_DEADLINE=y

CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n

#DFU Stuff
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_ZCBOR=y
CONFIG_MCUMGR=y
# CONFIG_BT_SMP=y


# add DSP libraries
CONFIG_CMSIS_DSP=y
CONFIG_CMSIS_DSP_STATISTICS=y
CONFIG_FORCE_NO_ASSERT=y
#CONFIG_BT=y
#CONFIG_BT_PERIPHERAL=y
CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS=y

#TDCS Stuff
CONFIG_ADC=y
CONFIG_NRFX_SAADC=y

# watchdog
CONFIG_WATCHDOG=y
CONFIG_WDT_DISABLE_AT_BOOT=y

My mcuboot.conf file:

CONFIG_BOOT_SIGNATURE_KEY_FILE="C:/Users/NolanGeer/Documents/GitHub/nrf5340_firmware/keys/nirskey.pem"
# Enable flash simulator
CONFIG_FLASH_SIMULATOR=y
CONFIG_FLASH_SIMULATOR_DOUBLE_WRITES=y
CONFIG_FLASH_SIMULATOR_STATS=n
CONFIG_NORDIC_QSPI_NOR=y
CONFIG_NORDIC_QSPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE=16

CONFIG_MAIN_STACK_SIZE=10240
CONFIG_BOOT_MAX_IMG_SECTORS=256


CONFIG_NRF53_MULTI_IMAGE_UPDATE=y
CONFIG_UPDATEABLE_IMAGE_NUMBER=2

CONFIG_BOOT_UPGRADE_ONLY=y
CONFIG_BOOT_IMAGE_ACCESS_HOOK_NRF5340=y
CONFIG_BOOT_IMAGE_ACCESS_HOOKS=y

I have to figure out what changed, but my RTT logging showed that my BLE initiated properly, and then the FOTAing worked!

Do you know how to only use internal flash? My coworker told me that we don't have an external flash on our real device (non-DK board), so we have to develop without one.

Thanks so much for your help thus far!

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Sigurd Hellesvik — Wed, 20 Sep 2023 06:37:32 GMT

[quote user="Nolan_G"]I believe this is the root of the problem, but I'm not sure how to fix it due to the nature of the warnings. Here is a photo:[/quote]

Those are a lot of warnings yes.
I do not use the "Problems" tab in VS Code, but I think it does not always know the full picture.
Can we instead copy me the full log from the Terminal? I show which log I mean in this video:

devzone.nordicsemi.com/.../case314711_5F00_recording.mp4I think most of your warnings are set because the stuff does not have DTS enabled for their peripheras, such as:

I think a lot of those are because you build for the DK, and as you say the DK does not have all peripherals connected/enabled.
Can you see if you get the same warnings when buliding for the custom board?

From your warnings, these seem the most relevant here:

Try to set

/ {
	chosen {
		nordic,pm-ext-flash = &mx25r64;
	};
};

inside child_image/mcuboot.overlay. Maybe it sets some stuff automatically.

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Tue, 19 Sep 2023 18:44:54 GMT

Okay, I have some small logs!

*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Successfully initialized I2C.
Failed to set regulator config.
PMIC READ: 0x00
Failed to read MAX20303 interrrupt registers.
Failed to read MAX20303 status registers.
Unable to initialize the MAX20303 PMIC.
FG READ Voltage: 0 mV
Unable to initialize the MAX20303 FG.
UNIX Time: 216505328339
ERROR: Unable to initialize the PCF85263A RTC.

It does seem that the application fails to boot, and it appears to be due to my PMIC not being initiated.

I believe this has to do with my SPI also not being initiated due to some Kconfig warnings.

EDIT: My coworker told me this is because my DK isn't connected to any peripherals, so those errors are expected. He said they're connected via I2C, so they have nothing to do with SPI. He also said they shouldn't have anything to do with Bluetooth. I'll enable deeper levels of logs to get the BLE details.

[quote userid="106736" url="~/f/nordic-q-a/103845/nrf5340-getting-fota-to-work-with-both-app-core-and-net-core-simultaneously/446590"]Keep a watch on your build logs though, sometimes they complete with warnings such as "CONFIG____ was ignored because of SOME_OTHER_CONFIG", so what you set is not always what ends up in the build folder.[/quote]

I believe this is the root of the problem, but I'm not sure how to fix it due to the nature of the warnings. Here is a photo:

Most of these say "missing dependencies: n" which is unresolvable, and some of the other have missing dependencies that "can't be set" manually.

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Sigurd Hellesvik — Tue, 19 Sep 2023 08:02:33 GMT

[quote user="Nolan_G"]d my pristine build takes about 3min 30sec, so it's painful to change one by one without knowing what I'm actually changing. I[/quote]

Ah yep, I know that feeling all too well.

Not saying you should change, but just as a FYI: but did you know that our stuff builds faster on linux? I even have some colleguas using WSL to build on windows, as it speeds up builds.

[quote user="Nolan_G"]Duplicate values won't be set twice and/or will have a squiggly line to indicate removing them, so I'm assuming this is okay to do.[/quote]

I agree.

Keep a watch on your build logs though, sometimes they complete with warnings such as "CONFIG____ was ignored because of SOME_OTHER_CONFIG", so what you set is not always what ends up in the build folder. You can also double check that everything is set in build/zephyr/.config and build/mcuboot/zephyr/.config.

[quote user="Nolan_G"]Also, some important information, multi-image FOTAing used to work with my application in SDK 2.2.0, and I enabled dfu with these lines.[/quote]

Interesting. If i remember correctly, I think that there was some changes to QSPI drivers in-between these versions. But you did not use external flash in your custom board so maybe not that then.

[quote user="Nolan_G"]I'll try enabling and viewing Logging, and I'll let you know what I find![/quote]

Yea, I think logging is the way to go here. I have seen a lot of error logs from the bootloader, so if I see yours, I think I will be able to tell you what is wrong.

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Tue, 19 Sep 2023 07:09:41 GMT

Thanks again for the response, Sigurd!

[quote userid="106736" url="~/f/nordic-q-a/103845/nrf5340-getting-fota-to-work-with-both-app-core-and-net-core-simultaneously/446562"]Hold on, do you not use git?[/quote]

Haha, I do use git. I have about 6 branches of different commits in different stages right now. I'm hesitant to change Kconfig values because I don't understand all of them, and my pristine build takes about 3min 30sec, so it's painful to change one by one without knowing what I'm actually changing. I should definitely sit and patiently read through what every option does so that I can have a better idea about what I'm doing, though.

[quote userid="106736" url="~/f/nordic-q-a/103845/nrf5340-getting-fota-to-work-with-both-app-core-and-net-core-simultaneously/446562"]So what I want to know is this: Is it only BLE from the app that does not work, or does no part of the app work? If only some parts of the app work, which? Logging would be a nice tool to figure this out.[/quote]

I'm actually not sure if the rest of the app is working since connecting to Bluetooth is typically what I do before trying any of the other modules.

In its current state, before adding any changes to make multicore FOTAing work, my application can be detected on BLE and connected to without the configuration changes from the sample application I linked as well as the sample application you linked. So, basically, my application without any changes can be seen on BLE, but when I try my app + either of the samples' Kconfig settings, it's no longer detectable. I actually, literally, append the prj.conf from the sample to the end of my prj.conf, as well as the mcuboot.conf to the end of my own mcuboot.conf. In the sample, the mcuboot.conf isn't called mcuboot.conf but rather it's a .conf within a board name folder within a mcuboot folder. These seem to have functioned the same. Duplicate values won't be set twice and/or will have a squiggly line to indicate removing them, so I'm assuming this is okay to do.

Also, some important information, multi-image FOTAing used to work with my application in SDK 2.2.0, and I enabled dfu with these lines.

void dfu_init(void)
{
    os_mgmt_register_group();
    img_mgmt_register_group();

    smp_bt_register();
}

I'll try enabling and viewing Logging, and I'll let you know what I find!

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Sigurd Hellesvik — Tue, 19 Sep 2023 06:42:29 GMT

[quote user="Nolan_G"]

The sample seemed to work with it enabled though, which was a bit confusing.

[/quote]

That is because the external flash enabling in the Partition manager sets up some stuff automatically, which are also needed for internal flash. So in current versions of the SDK, you kindof need it either way.

[quote user="Nolan_G"]Yes, the Bluetooth works for the sample project I'm using for FOTAing as well as a sample project for Bluetooth mesh. These are a bit fancier than plain Bluetooth firmware but they show that the Bluetooth works regardless.[/quote]

Nice nice! Just wanted to make sure the antenna on the custom board actually worked. Have had tickets before where we debugged software only for the issue to be hardware.

[quote user="Nolan_G"]I do not believe so. The build completes in VSCode, and that's the only logging we have. I've enabled debugging logs in prj.conf before, but I'm not sure where those are output to. I've not seen them before.[/quote]

Not only for bootloaders, I advise you to have logging output from your nRF chip. It will make it a lot easier to debug issues, for example the current issue. See Logging in nRF Connect SDK for docs on this. UART and RTT are the most used alternatives. For custom board, you have not always routed out an UART for logging, so then you may have to use RTT, whcih can be used via a debugger.
Making RTT work with the bootloader is a bit tricky, so if you need that, I suggest you first try it from the DK. I can help doing that if needed.

[quote user="Nolan_G"] and I'm hesitant to change any Kconfig values since I know that I can break the build easily. [/quote]

Hold on, do you not use git?
If you do use git, can you commit your current progress to something (testing branch or whatever), and it will be saved.
If you do not use git, I highly recommend that you use any kind of version control.

[quote user="Nolan_G"]o if the sample project can display on Bluetooth then I'm not sure why mine can't.[/quote]

Maybe your project crashes before it gets to the application?
The DK has external flash, so if the bootloader can not find external flash and therefore crashes, it will not run the application. Or something similar like that.
So what I want to know is this: Is it only BLE from the app that does not work, or does no part of the app work? If only some parts of the app work, which? Logging would be a nice tool to figure this out.

[quote user="Nolan_G"]Also, what exactly is happening when I select "Confirm and Test" instead of "Confirm Only"? How is it "confirming" the images? What is being tested?[/quote]

See my repo explaining test or confirm. "Test & Confirm" mode will first tag the image as Test, then reboot the device to swap, and then tag the image as confirm. This is so that if the new image crashes, the bootloader will revert to the old one, which we know works. It is a feature to not break the device with a broker update.

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Mon, 18 Sep 2023 15:42:43 GMT

Also, what exactly is happening when I select "Confirm and Test" instead of "Confirm Only"? How is it "confirming" the images? What is being tested?

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Nolan_G — Mon, 18 Sep 2023 15:38:52 GMT

Hi Sigurd, thanks for the reply!

For your first question,

[quote userid="106736" url="~/f/nordic-q-a/103845/nrf5340-getting-fota-to-work-with-both-app-core-and-net-core-simultaneously/446457"]

Does it behave as expected if you only "Confirm" and reset manually?

[/quote]

it does, actually! I'm not sure why I hadn't tried this before. It seems my debugging skills are failing me. I've been tunnel-visioning on changing Kconfig values for a little over a week now, so my head is stuck in the weeds!

[quote userid="106736" url="~/f/nordic-q-a/103845/nrf5340-getting-fota-to-work-with-both-app-core-and-net-core-simultaneously/446457"]Let me know what you would expect and I can try to guide you to how to fix that.[/quote]

Honestly, my goal is to just get FOTAing both cores to work as easily as possible. My coworker told me we didn't have an external flash and we disabled our QSPI as you can see in our prj.conf file. The sample seemed to work with it enabled though, which was a bit confusing.

[quote userid="106736" url="~/f/nordic-q-a/103845/nrf5340-getting-fota-to-work-with-both-app-core-and-net-core-simultaneously/446457"]

Can you see Bluetooth on your own device with simple Bluetooth firmware, not any bootloader or anything fancy?

[/quote]

Yes, the Bluetooth works for the sample project I'm using for FOTAing as well as a sample project for Bluetooth mesh. These are a bit fancier than plain Bluetooth firmware but they show that the Bluetooth works regardless.

[quote userid="106736" url="~/f/nordic-q-a/103845/nrf5340-getting-fota-to-work-with-both-app-core-and-net-core-simultaneously/446457"]

Do you get any error logs from your app or bootloader?

[/quote]

I do not believe so. The build completes in VSCode, and that's the only logging we have. I've enabled debugging logs in prj.conf before, but I'm not sure where those are output to. I've not seen them before.

It seems like I'm very close to getting my project to work on FOTA, and I'm hesitant to change any Kconfig values since I know that I can break the build easily. I have every property to display on Bluetooth, because I copied the sample's prj.conf and added them to the end of my own prj.conf, so if the sample project can display on Bluetooth then I'm not sure why mine can't. It was displaying before, so something may have changed it.

Thanks for helping me with this!

All the best,

Nolan Geer

RE: nRF5340 Getting FOTA to work with both app core and net core simultaneously

Sigurd Hellesvik — Mon, 18 Sep 2023 12:50:12 GMT

Hi Nolan,

Let's see if we can make this work.

First, I will comment on your ticket, and ask some questions.

[quote user=""]However, a coworker told me he was able to partition the internal flash on our DK boards to support FOTAing without external flashing. [/quote]

You can do it with internal flash, but thing is, the "nordic,pm-ext-flash = &mx25r64;" configuration enables a lot of stuff automatically in the background, so this is easier to start with.

We are working on adding it more easily in these PRs:

https://github.com/nrfconnect/sdk-nrf/pull/10060

https://github.com/nrfconnect/sdk-mcuboot/pull/235

If you want to use internal flash for now, I think you can have a look this sample:

devzone.nordicsemi.com/.../peripheral_5F00_lbs_5F00_dfu_2800_2_2900_.zip

[quote user=""]When I would first start the DFU, after I clicked "Confirm and Test" i[/quote]

From my repo:

Does it behave as expected if you only "Confirm" and reset manually?

That being said, it should be possible to automate this more, but you may have to enable more functionality for the project in that case. Let me know what you would expect and I can try to guide you to how to fix that.

[quote user=""]For my own project, currently I'm able to build and flash my board, but I can't see it being listed as a Bluetooth device to connect to.[/quote]

Can you see Bluetooth on your own device with simple Bluetooth firmware, not any bootloader or anything fancy?

Do you get any error logs from your app or bootloader?

Regards,
Sigurd Hellesvik