Nordic ESL Presentation ,Implementation and Reccomendation

[Sankton]

Dear Nordic 

Last week our team concluded with PAwR functionality and achieved the communication between AP and Peripheral . We asked Nordic on private ticket( https://devzone.nordicsemi.com/support/338373) on how to see logs in nrf5340 when network core was flashed with peripheral code . 

But instead we were asked to follow nordic's ESL documentation and presentation which uses 52833 as peripheral and 5340 as AP . (using https://github.com/NordicPlayground/nrf-esl-bluetooth/tree/v2.5-branch) 

We followed what nordic suggested but when it came to flashing esl_peripheral code we realized only following boards had support for this example those are 52840,52833,52832,54l15.

We were promised that that example will work for 5340 also . As our organization already has a developed product that is integrated with EPD that is based on 5340 .

In esl_peripheral there is no support for 5340 . 

Can you give a work around here to use this example on our 5340 Soc please ?

Also please tell us the way or method using sys build to flash an application on application core and network application on network core of 5340 and see RTT logs for both .


Thanks and Regards
S  

[Kenneth]

Hi again,

We asked Nordic on private ticket( https://devzone.nordicsemi.com/support/338373) on how to see logs in nrf5340 when network core was flashed with peripheral code . 

But instead we were asked to follow nordic's ESL documentation and presentation which uses 52833 as peripheral and 5340 as AP . (using https://github.com/NordicPlayground/nrf-esl-bluetooth/tree/v2.5-branch) 

Sorry, that might have been a misunderstanding from me, but I thought using the "Getting started with Bluetooth Electronic Shelf Labels (ESL) and Periodic Advertising with Responses (PAwR)" was a good idea if you were interested in ESL. If your only problem was to get log from network core, then no need to follow that guide, instead you can build the netcore with logging just as you would to for the appcore, but make sure to place the kconfig options to enable logging in for the netcore image (using conf file in child image or sysbuild depending on ncs version). Be aware that if you want to log both appcore and netcore at the same time, then you need either two uarts (one for each core) or 1uart+rtt (e.g. rtt from appcore and uart from netcore). The logging backend is controllable by kconfig options that must be placed in the appropriate image you want logging from. 

Depending on which ncs version you want to use, it may differ a bit on whether using child_image or sysbuild on how to apply the config options for the netcore. But if you for instance search for nrf5340dk_nrf5340_cpunet.conf in ncs, you can find for instance how you can apply configuration to the netcore (also see how that file is placed relative to the application). Normally I don't expect logging is enabled by the netcore, since it's pretty much delivered by us and not much you need to debug from it, though there are several configurations that affect the bluetooth controller that is useful to configure in the netcore.

So overall, you may consider skip using what I linked to (or use it as reference), and instead go back to what you had working already on the nRF5340.

Sorry for the confusion.
Kenneth