Visual Code issues

While using Visual Code I have noticed that:

  • First compile always generates errors, which is fine. The error notifications are persistent even after they have been fixed. The only thing that clears these errors is exiting Visual Code and restarting the program.
  • Adding a second build within the same project consistently cause all builds to fail with missing file errors
  • While creating custom applications, such as the Hello World App from the DevAcademy, the printk function does not output to any terminal. Also the DevAcademy still references the NRF Terminal, which has been removed
  • Many of the sample applications or examples do not copy over correctly into target directories with several files having hard coded directory paths which are not valid due to the path move

These are annoyances and can be worked around but having to close and reopen VC to clear errors is troublesome and not being able to reliably create multiple builds in the same project without bricking the original build is limiting the versatility of the system.

  • Hi

    What you say about using the Zephyr drivers is true, but there are cases where we will want to have finer control over timing and utilize hardware specific to the nRF chips which is not a part of Zephyr. For my development this is not the case but I am sure others will require low level access to nrfx for such things as tight timing and utilization of DPPI/PPI. The DevAcademy courses also reference this particular requirement. 

    In this thread I am just pointing out places where the supplied examples cause issues and hang up. I can work around these issues. As I come across new "hick-ups" I will post them.

    Cheers

Related