MikroElektronika Forum

I have installed some click cards such as Led_Ring_R click, 7x10 Y click and GNSS 4 click and I get the same error (error 340) I don't know how to solve it. I have doubts about Mikrobus. I have version 1.0 installed and the EasyPicV7 connectivity development board.
On this Board, I found only mikrobus available for the pic18f45k22.
Is it possible to use another microcontroller such as pic18f4620?
The manual does not give details about these compatibilities.

Sos.
Thanks

Hi,

You need to find the path to the EasyPIC v7 BDF API.

Go to Project and Edit Search Paths. Now you need to click on the three dots and add the Uses file in Projects MikroBus BDF API folder (for both c and h). Click APPLY and then OK.

Regards,

Ivan.

Thank you in advance for your help. That's OK, it works. Nice.

I have a lot of questions.

The first one:
Hi, I’m trying the example from libstock for Click_GNSS 4. The example says "MCU : P18F87K22, Dev, Board :EasyPicPRO V7", but I have Dev. Board EasyPic V7 Connectivity with Pic 45K22.

In the figures show some attempts where I change the checkbox in mikroBus BDF API and I get different errors.

The first figure shows the errors I got because there is not enough memory.

In the second figure I got 'Undeclared identifier mikrobus_logWrite'. But 'mikrobus_logWrite' is not in mikroBUS API BDF.


The second one:
In another case I also got the error Undeclared identifier 'mikrobus_uartInit'. I have checked the pld file and ENABLE_LOG and ENABLE_UART are found there.

The last one:
And the biggest question I have. in Library Manager, -> mikroBUS BDF API there are not all the commands such as mikrobus_uartInit and mikrobus_logWrite
All commands should be in the Mikrobus BDF API. That depends on the support on the development board, on the Microntroller. I don't understand that.

Thank you in advance for your help.

Hi,

When building try to use Rebuild all sources, also try downloading the mikroSDK library.
https://libstock.mikroe.com/projects/view/2249/mikrosdk

You will need to Package Manager to install the library, you can also use the Package Manager to install the library for an MCU that might not be covered by the library, you just find the MCU in the list and check it.
https://www.mikroe.com/package-manager

The libraries will not work for every MCU.

The not enough RAM just means that your MCU does not have enough RAM for the given example, you can try to remove some parts of the example to make it fit.

Regards,

Ivan.