Timer issue with getting external flash binding

[Ubaid_M]

Hi,

I am using nRF52833 & nCS for an application development,

I am facing a curious issue where, if i enable printk in nCS build, I am getting SUCCESS on calling device_get_binding() to an external flash device.

While if i disable printk in nCS build, the same device_get_binding() is returning err = 19.

I do not want to retain printk, kindly suggest how to solve this.

[Simonr]

Hi

In what file and code line does your application call the device_get_binding() function? This function iterates through the devices on the system. If a device with the given name field is found, and that device initialized successfully at boot time, this function returns a pointer to the device. To debug, it's best to set a breakpoint on your device driver's init function. Perhaps there is something in your application requiring printk. Is it the same call both if you enable and disable printk? Error 19 points to there being "no such device". 

What nRF Connect SDK version are you using, and is your project based on one of our samples?

Best regards,

Simon

[Ubaid_M]

Hello Simonr,

I am using device_get_binding() function, in a C++ application file as:

Here I device_get_binding() is returning 19, if in printk() definition I am calling return; as soon as execution enters printk().

If I am removing return statement from printk(), the device_get_binding() returns 0.

[Simonr]

Hi

What version of NCS are you using here? And what do you mean by "if I am removing return statement from printk(), the device_get_binding() returns 0"? Is the device_get_binding successful if you're not adding these printk() functions?

Best regards,

Simon

[Ubaid_M]

Hello Simonr,

Simonr said:

And what do you mean by

What I mean is, as in printk definition below:

I added a return statement on line number 1 in the above definition.

So the revised definition of printk applies everywhere.

Now with this revised definition, the device_get_binding() returns 19.

[Simonr]

Hi

If you're calling multiple printk functions in your application after disabling the printk that is likely to cause issues. Is there a reason you have printk() function(s) if your plan is to disable printk altogether?

Best regards,

Simon