Keil uVision V5 Legacy Nordic Project Compile Errors

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

adnankhalid — Fri, 27 Jan 2023 14:27:36 GMT

Noted and thank you for your input!

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

Simonr — Fri, 27 Jan 2023 14:22:55 GMT

That seems to be what you're discussing with Torbjørn in this case. There is no point in having two cases on the same topic open at the same time. Torbjørn is the creator of the image transfer demo, and I think he will be able to help you out here. Let's close this and focus on your other ticket instead.

Best regards,

Simon

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

adnankhalid — Fri, 27 Jan 2023 13:58:29 GMT

Hello Simon,

So a few things:

I was aware of this issue with SEGGER and was indeed pressing the RESET. However this doesn't solve the issue.

I am indeed able to see the device advertising once I comment out the camera_init() function.

I have always suspected that the SPIM/TWIM segment is where the issue lies. I need support to debug that segment of the code base.

Please advise.

Thanks,

Adnan

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

Simonr — Fri, 27 Jan 2023 11:20:58 GMT

Hi Adnan

So, this is apparently an issue with SEGGER Embedded Studio that I wasn't aware of. When flashing an application onto a board, the debugger won't perform a full reset, instead it will start the program from the application start address. So after pressing the reset button on the DK for example, the application will run as expected. An alternate fix is to run an nrfjprog --eraseall command before you program the application onto your board.

After doing so, the application runs as expected (if you have a camera connected that is). Or else it will be stuck in the camera_init(). To make sure that it's advertising, you can comment out the camera_init() and you'll be able to see the device advertising.

Best regards,

Simon

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

adnankhalid — Thu, 26 Jan 2023 14:31:30 GMT

Hello Simon,

Please see the attached project below.

Thanks,

Adnan

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

Simonr — Thu, 26 Jan 2023 10:11:01 GMT

Okay, can you upload your project here so we can take a look at it. There must be some changes made on your end that enables the SoftDevice twice at some reason. That should be the only reason for this INVALID_STATE error to trig when enabling the BLE stack. I'm assuming you don't have a bootloader as part of your project as you're not sure what I mean about it.

Best regards,
Simon

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

adnankhalid — Wed, 25 Jan 2023 18:08:36 GMT

Hello Simon,

The ble_stack_init() is only called once in the main function. The RAM and Flash memory values being used are:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x26000

FLASH_SIZE=0x5a000

RAM_START=0x20004010

RAM_SIZE=0xd568

This line: "when a bootloader has been used before the main application to do DFU over BLE, that has not disabled the SoftDevice after being done and just directly jumped into the main application." Is confusing I am not sure what you mean, also if this is the case how do I fix it?

Lastly, this issue seems to disappear when I am in debug mode.

Please advise.

Thanks,

Adnan

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

Simonr — Wed, 25 Jan 2023 08:20:53 GMT

After another look, the INVALID_STATE from the nrf_sdh_enable_request(); function should only be triggered if the SoftDevice is already enabled somehow.

ret_code_t nrf_sdh_enable_request(void)
{
    ret_code_t ret_code;

    if (m_nrf_sdh_enabled)
    {
        return NRF_ERROR_INVALID_STATE;
    }

This is usually due to the ble_stack_init() being called twice or when a bootloader has been used before the main application to do DFU over BLE, that has not disabled the SoftDevice after being done and just directly jumped into the main application. The RAM and Flash memory for specific releases can be found in the release notes downloadable here, but they are these should be correct for v7.0.1 as well.

Best regards,

Simon

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

adnankhalid — Tue, 24 Jan 2023 14:40:47 GMT

Hello Simon,

So I checked and please note the following:

1) The Additional Load File [0] does indeed point to the SoftDevice recommended for the project S132

2) The preprocessor definitions are as follows:

BOARD_PCA10040

CONFIG_GPIO_AS_PINRESET

FLOAT_ABI_HARD

INITIALIZE_USER_SECTIONS

NO_VTOR_CONFIG

NRF52

NRF52832_XXAA

NRF52_PAN_74

NRF_SD_BLE_API_VERSION=6

S132

SOFTDEVICE_PRESENT

SWI_DISABLE0

OV5642_MINI_5MP

3) The RAM and Flash start values I took from the Keil settings and are as follows:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x26000

FLASH_SIZE=0x5a000

RAM_START=0x20004010

RAM_SIZE=0xd568

The Adjustment of RAM and Flash memory note doesn't have any values for S132 V7.0.1 so I am using the above values.

After all that I am still getting the error:

<info> app: Start Main. Initialize BLE components...
<info> app: Timer Init: YES
<info> app: Buttons LED Init: YES
<info> app: ble_stack_init(void): ENTER
<debug> nrf_sdh: State request: 0x00000000
<debug> nrf_sdh: Notify observer 0x00035D08 => ready
<debug> nrf_sdh: State change: 0x00000000
<error> app: ERROR 8 [NRF_ERROR_INVALID_STATE] at C:\Nordic\sdk\nRF5SDK160098a08e2\examples\nrf52-ble-image-transfer-demo-master_segger\main.c:464
PC at: 0x0002789F

I have tried doing a RESET on the DK board but with no luck.

Please advise.

Thanks,

Adnan

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

Simonr — Tue, 24 Jan 2023 13:29:00 GMT

Hi Adnan

Yes, you need to configure the SoftDevice as well. First off, make sure that the Additional Load File [0] in your Loader (in project options) points to the correct place where your SoftDevice is located, as well as the preprocessor definitions include the following defines:

NRF_SD_BLE_API_VERSION=6

S140

SOFTDEVICE_PRESENT

Lastly, you should check out this RAM and Flash adjustment guide to make sure your applications RAM and Flash is configured to fit the SoftDevice you're using as well: Adjustment of RAM and Flash memory

Best regards,
Simon

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

adnankhalid — Mon, 23 Jan 2023 18:29:28 GMT

Hello Simon,

Thank you for the follow up. I took your advise and switched to Segger Embedded Studio over the weekend. I managed to get the project setup and had to modify the common include paths and paths in the .emProject file but now the project compiles and am able to download it onto the nRF52 DK eval board. So thank you for your guidance on this issue.

The issue I am now having is that I get the following error on the J-Link RTT Viewer:

00> <error> app: ERROR 8 [NRF_ERROR_INVALID_STATE] at C:\Nordic\sdk\nRF5SDK160098a08e2\examples\nrf52-ble-image-transfer-demo-master_segger\main.c:463
00> PC at: 0x0002786D
00> <error> app: End of error report

The line number points to the following function:

/**@brief Function for the SoftDevice initialization.
*
* @details This function initializes the SoftDevice and the BLE event interrupt.
*/
static void ble_stack_init(void)
{
ret_code_t err_code;

err_code = nrf_sdh_enable_request();
APP_ERROR_CHECK(err_code);

// Configure the BLE stack using the default settings.
// Fetch the start address of the application RAM.
uint32_t ram_start = 0;
err_code = nrf_sdh_ble_default_cfg_set(APP_BLE_CONN_CFG_TAG, &ram_start);
APP_ERROR_CHECK(err_code);

// Enable BLE stack.
err_code = nrf_sdh_ble_enable(&ram_start);
APP_ERROR_CHECK(err_code);

// Register a handler for BLE events.
NRF_SDH_BLE_OBSERVER(m_ble_observer, APP_BLE_OBSERVER_PRIO, ble_evt_handler, NULL);
}

I am wondering if the SoftDevice needs to be configured as I have not done anything with respect to that.

Please advise and thanks!

Adnan

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

Simonr — Mon, 23 Jan 2023 08:48:11 GMT

Okay, can you try making sure the relative paths in your project (both to driver/library files and DeviceFamilyPack) are long enough with the same amount of "..\..\" that it is to the root of your path. It could be an issue with the Device Family Pack you're using as well, as we had some issues with them in some of the later SDK versions on the nRF5 SDK side. If you're not able to figure out the issue from editing the paths I would suggest trying out SEGGER Embedded Studios to see if you can build/flash the project there.

Best regards,

Simon

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

adnankhalid — Fri, 20 Jan 2023 15:08:00 GMT

Hello Simon,

Thank you for getting back to me on this.

I did initially start with the new nRF Connect SDK but unfortunately the camera requirement and time constraint for our eval process forced me to get this legacy sample up and running.

I can switch to the SEGGER Emb. Studio if necessary.

Currently the file structure is as follows:

Project itself:

C:\TPR-Nordicsemi-Sources\Keil\Projects\nrf52-ble-image-transfer-demo-master

Nordic SDK + SoftDevice:

C:\Nordic\sdk\nRF5SDK160098a08e2

C:\Nordic\sdk\s132nrf52701

Keil Device Family Pack:

C:\Users\NOVA-00002\AppData\Local\Arm\Packs\NordicSemiconductor\nRF_DeviceFamilyPack\8.44.1

For the Keil Install. I used the defaults paths as per the installation process.

Please advise.

Thanks,

Adnan

RE: Keil uVision V5 Legacy Nordic Project Compile Errors

Simonr — Fri, 20 Jan 2023 13:13:54 GMT

Hi Adnan

These errors make it seem like the project isn't in the correct folder in your SDK, so that it's not able to find the driver/header files where these functions are defined. Where is the project located, and what is the relative path in your preprocessor definitions set to?

If you're just doing evaluation, please note that we generally recommend new designs to use the nRF Connect SDK instead of the nRF5 SDK. More information in the nRF Connect SDK statement here.

It's also worth noting that if you're using the nRF5 SDK, SEGGER Embedded Studio is in our opinion a better IDE to use for development, as you get a free license when using Nordic products, and our expertise in SES is generally better than with Keil.

Best regards,

Simon