Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Simonr — Tue, 04 May 2021 07:37:46 GMT

The LPN example in the Mesh SDK uses the DFU from the nRF5 SDK, and we have a section on how you can configure DFU over BLE using the LPN example here. Alternatively, you can check out and implement the DFU example in the Mesh SDK and its user guide.

Best regards,

Simon

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Tomlee — Fri, 30 Apr 2021 10:16:29 GMT

Hi Simonr,

Thanks for your reply.

so you're working on implementing Mesh into the USB/DFU project you've created, correct?

===yes

Can you confirm that you've followed the Bluetooth Mesh user guide to integrate Mesh into nRF5 SDK examples?

====yes

What SDK version (both nRF5 SDK and Mesh SDK version) are you using?

===nRF52 SDK: 16.0.0

===Mesh SDK: 4.2.0

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Simonr — Thu, 29 Apr 2021 07:09:10 GMT

Okay, so you're working on implementing Mesh into the USB/DFU project you've created, correct? Can you confirm that you've followed the Bluetooth Mesh user guide to integrate Mesh into nRF5 SDK examples? What SDK version (both nRF5 SDK and Mesh SDK version) are you using?

Best regards,

Simon

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Tomlee — Thu, 29 Apr 2021 00:52:17 GMT

Hi Simonr,

initialize() and start() are about Mesh

static void mesh_init(void)
{
    mesh_stack_init_params_t init_params =
    {
        .core.irq_priority       = NRF_MESH_IRQ_PRIORITY_LOWEST,
        .core.lfclksrc           = DEV_BOARD_LF_CLK_CFG,
        .models.config_server_cb = config_server_evt_cb
    };

    uint32_t status = mesh_stack_init(&init_params, &m_device_provisioned);
    switch (status)
    {
        case NRF_ERROR_INVALID_DATA:
            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Data in the persistent memory was corrupted. Device starts as unprovisioned.\n");
            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Reset device before starting of the provisioning process.\n");
            break;
        case NRF_SUCCESS:
            break;
        default:
            ERROR_CHECK(status);
    }

#if 1//NRF_MESH_SERIAL_ENABLE
ERROR_CHECK(nrf_mesh_serial_init(NULL));
#endif

m_evt_handler.evt_cb = mesh_evt_handler;
nrf_mesh_evt_handler_add(&m_evt_handler);
}

static void initialize(void)
{
ERROR_CHECK(app_timer_init());
hal_leds_init();

__LOG_INIT(LOG_MSK_DEFAULT | LOG_SRC_DFU | LOG_SRC_APP | LOG_SRC_SERIAL, LOG_LEVEL_INFO, log_callback_rtt);
__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "----- Bluetooth Mesh DFU Example -----\n");

ble_stack_init();

mesh_init();

__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Initialization complete!\n");
}

static void start(void)
{
    if (!m_device_provisioned)
    {
        static const uint8_t static_auth_data[NRF_MESH_KEY_SIZE] = STATIC_AUTH_DATA;
        mesh_provisionee_start_params_t prov_start_params =
        {
            .p_static_data = static_auth_data,
            .prov_complete_cb = NULL,
            .prov_device_identification_start_cb = NULL,
            .prov_device_identification_stop_cb = NULL,
            .prov_abort_cb = NULL,
            .p_device_uri = EX_URI_DFU
        };
        ERROR_CHECK(mesh_provisionee_prov_start(&prov_start_params));
    }

#if 1//NRF_MESH_SERIAL_ENABLE
__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Enabling serial interface...\n");
ERROR_CHECK(nrf_mesh_serial_enable());
#endif

mesh_app_uuid_print(nrf_mesh_configure_device_uuid_get());

ERROR_CHECK(mesh_stack_start());

    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "DFU with usb driver example started!\n");
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "bootloader_id is 255\n");
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "application_id is 255\n");
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "other is same with srd3_radar_sensor\n");
}

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Simonr — Tue, 27 Apr 2021 12:42:33 GMT

What does the initialize() and start() functions call to exactly? I need some details as to what they do. Do you see the same error if you call the initialize() but not start()?

Best regards,

Simon

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Tomlee — Tue, 27 Apr 2021 02:10:58 GMT

Hi,

I just want to implement DFU function.

1) Plug a Dongle with a USB port into My PC (Dongle's usb connect to D- and D+ of nRF52)

2) send fw to Dongle from PC

3) Donle receive fw data , then send data out to update other node with ble mesh

Is there any example to reference?

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Tomlee — Tue, 27 Apr 2021 01:04:09 GMT

Hi Simonr,

Thnaks for your reply.

I have already merge usb cdc modules fie to ..\examples\dfu\dfu_nrf52833_xxAA_s113_7_0_1.emProject , if I comment

initialize() and start() in main() of main.c of this project(as follow code), then there no error

"app_error_weak.c, 115, Mesh error 133 at 0x00000000 (:0)".

the USB cdc modules works well, since I can see "USB CDC ..." com port in manage device of my pc.

when cancel commnet initialize() and start()，the error happens again.

Do you think what reason it will be?

  int main(void)
{
   // initialize();
   // start();

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Simonr — Mon, 26 Apr 2021 12:57:43 GMT

Yes, it should be possible to modify the USB CDC ACM project to fit the nRF52833 without to many problems. Please refer to the Developing for nRF52811 user guide and the "Transferring to nRF52811 HW". The process will be similar for the nRF52833, but the names with nRF52811 should be replaced with nRF52833, and the ROM and RAM end addresses will have to match the nRF52833 RAM and Flash memory sizes.

The app_error_weak.c, 115, Mesh error 133 at 0x00000000 (:0) message does not seem related to this merge however, as it suggests that you've tried implementing Bluetooth Mesh into the nRF5 SDK as well. Can you confirm this?

Please start out by just modifying the USBD_cdc_acm example to fit the nRF52833, and then move onto merging more examples, as it will get very hard pinpointing your problem if you do a bunch of changes.

Best regards,

Simon

RE: Can I modify source code for the vitual com of nRF52833 USB CDC ACM in \examples\peripheral\usbd_cdc_acm?

Tomlee — Mon, 26 Apr 2021 08:50:45 GMT

I have already modified, it works well in nRF52388

but I have other question:

when I add usb cdc acm module files to ..\examples\dfu\dfu_nrf52833_xxAA_s113_7_0_1.emProject , and compile successful, then flash fw to EV board, it shows messasge, as follow:

app_error_weak.c, 115, Mesh error 133 at 0x00000000 (:0)

Could you tell me why it happens , please?