Thingy 53 does not enumerate serial port for Dev Academy Lesson 6 exercise 2

[Ramulous]

Currenty I am on version 2.1 and was able to get the Thingy 53 to enumerate serial port(s) but using the old version 1.x thingy53.c file and the include files and functions that are in that file.

Fullscreen thingy53.c Download

/*
 * Copyright (c) 2021 Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
 */

#include <zephyr/init.h>

#include <img_mgmt/img_mgmt.h>
#include <os_mgmt/os_mgmt.h>
#include <zephyr/mgmt/mcumgr/smp_bt.h>

#include <zephyr/usb/usb_device.h>

#include <zephyr/logging/log.h>
LOG_MODULE_REGISTER(thingy53_setup);


static int bt_smp_init(const struct device *dev)
{
	ARG_UNUSED(dev);
	int err = 0;

	img_mgmt_register_group();
	os_mgmt_register_group();

	err = smp_bt_register();

	if (err) {
		LOG_ERR("SMP BT register failed (err: %d)", err);
	}

	return err;
}

static int usb_cdc_init(const struct device *dev)
{
	int err = usb_enable(NULL);

	if (err) {
		LOG_ERR("Failed to enable USB");
	}

	return err;
}

SYS_INIT(bt_smp_init, APPLICATION, CONFIG_APPLICATION_INIT_PRIORITY);
SYS_INIT(usb_cdc_init, APPLICATION, CONFIG_APPLICATION_INIT_PRIORITY);

In order to get thingy53.c to compile I had to select Use build system default under configuration in the edit build configuration instead of prj.conf.  The prj.conf file is present anyway.  

I then uplevelled to version 2.4 and just flat out tried the solution directly from the Nordic Git Hub server and was not able to get the serial port to enumerate.  I tried using parts of the old 1.x solution specifically the thingy53.c file once again but no luck.  Did some reading and looks like the thingy53.c file is no longer necessary anyway.  What is the solution to get the Thingy53 to enumerate and what's the difference between picking build system default or prj.conf in the edit build configuration. I tried to attach ncs-fund-main/v2.x.x/lesson6  https://github.com/NordicDeveloperAcademy/ncs-fund here that doesn't enumerate a serial port so that  console functions will work like printk, the logger and so on.

I'm using Visual Studio Code and any other sugestions that I can find.

[Amanda Hsieh]

Hi, 

For NCS v2.4.0, you can use the thingy53_nrf5340_cpuapp.conf and thingy53_nrf5340_cpuapp.overlay under nrf\samples\bluetooth\peripheral_uart\boards.

Regards,
Amanda H. 

[Ramulous]

/Documents/Nordic/myapps/fund_less6_exer2_solutionNordic/prj.conf:33: warning: attempt to assign the value 'y' to the undefined symbol BT_NUS_UART_ASYNC_ADAPTER

This did not work as you can see the BT_NUS_UART_ASYNC_ADAPTER was undefined.  I need a super really small primitive project that can both transmit and receive uart data.  That's why Lesson 6 exercise 2 needs to work with 2.4 and in all future releases 2.5 and so on.  This project does not use Bluetooth.  Can you are someone take another stab.  Ideally you would test with that project (lesson 6 exerercise 2)   Thanks

[Amanda Hsieh]

Hi, 

Remove the CONFIG_BT_NUS_UART_ASYNC_ADAPTER=y. The USB CDC should work. 

Ramulous said:

That's why Lesson 6 exercise 2 needs to work with 2.4 and in all future releases 2.5 and so on.

Without modification, Lesson 6 Exercise 2 can work in v2.4.0. You can refer to https://github.com/NordicDeveloperAcademy/ncs-fund/tree/main/v2.x.x/lesson6/fund_less6_exer2_solution 

-Amanda H.

[Ramulous]

I had already tried removing the BT_NUS_UART_ASYNC_ADAPTER and the serial port still does not enumerate.  In addition the initial problem statement is that https://github.com/NordicDeveloperAcademy/ncs-fund/tree/main/v2.x.x/lesson6/fund_less6_exer2_solution 

does not enumerate the serial port so that I can use the logger printk and so on.  When you say it can work I asking then how can it work.  You should have said that it will enumerate.  I think you don't know what I mean by the serial port enumeration I will explain that next.

[Ramulous]

What the issue is and what I mean by serial port enumeration is that the serial ports show up in DeviceManager on a 64 bit Windows 10 machine.  Here is a good example from the nRF5340-DK (i.e. not the Thingy 53).  Here the nRF5340-DK is showing two serial ports COM 15 and COM 16.  This means that the nRF5340-DK has enumerated two serial ports COM 15 and COM 16.  Now I will power down the DK to show you that they are no longer enumerating.  

If the two figures came through and you can see them now you can see that the DK is no longer enumerating.  

That is what I mean that the THINGY 53 will not enumerate the serial port(s).  This is necessary to be able to use printk the logger and so on.  At the same time it would be nice to receive data through the port to the THINGY 53 as well but that is not part of the Lesson 6 exercise 2 unfortunately.

[Amanda Hsieh]

Hi, 

Please try my test project fund_less6_exer2_solution.7zfor NCS v2.4.0. 

It can enumerate the serial ports and get the log. I don't modify the code, just add the config and overlay files for Thingy53.

-Amanda 

[Ramulous]

Thank you I got both the lesson project and your project to work (enumerate serial port(s) ) by using the thingy53_nrf5340_cpuapp instead of thingy53_nrf5340_cpuapp_ns like I always have.  That is Cortex M security extensions (CMSE) is disabled to work and enabled it does not.  Some initial examples from Nordic unless I recall wrong the examples did use CMSE so I have been using the tool that way all the time.

I still need to point out that when we were using thingy53.c using thingy53_nrf5340_cpuapp_ns, CMSE enabled, the serial ports did enumerate.  So in essence, you may not have completely fixed the SDK by no longer needing thingy53.c  I think the serial ports should enumerate either way.  So in my opinion someone at Nordic should take a look at that.  Or explain to me the situation.

I also wonder in the Configuration pull down the difference between Use build system default and prj.conf is?  Because that would make a difference when we were still using the thingy53.c file.

 

Is there a document somewhere that guides us to upgrading to 2.4?

Thanks for your help.