Hello,
You can simply call the HAL routine, given you already know the size of the
HWID for your MCU (using LEN below):
#include
uint8_t buf[LEN];
len_read = hal_bsp_hw_id(buf, LEN);
"buf" will have the HWID and the len will be returned. If you want to do it in
a portable manner, you can
Hello,
Is there any driver for retrieving CPU hardware IDs in mynewt? I can see
that there is a sys/id package, but I couldn't find any documentation for
it, nor any use of this library in the sample code.
Amr
Hi Paul,
IMO Option 1 seems like the best option here. I don't think the special
command processing code will require a lot of work. Of course, if you think
that Option 2 is better for your use case you can implement it and submit a
PR.
BR
Michał Narajowski
pon., 25 cze 2018 o 04:10
+1
On Sun, Jun 24, 2018 at 7:45 AM, Jacob Rosenthal
wrote:
> TLDR
> why not make all newt core packages dependencies absolute like
> - "@apache-mynewt-nimble/nimble/host/util"
> instead of relative as they are now
> - nimble/host/util
>
> Whenever I need to fork locally to my project I
Not sure I have a strong opinion on this one. My initial reaction was option 1
but I can understand why some of the other options might be better.
> On Jun 25, 2018, at 4:07 AM, Michał Narajowski
> wrote:
>
> Hi Paul,
>
> IMO Option 1 seems like the best option here. I don't think the
All:
I'm using a BroadCom(Cypress)43438 Bluetooth chip that receives a 4 wire HCI.
I got one response that said I just have to change the syscfg setting in my
target to
BLE_HCI_TRANSPORT_NIMBLE_BUILTIN: 0
BLE_HCI_TRANSPORT_UART: 1
1. I can't find any documentation to what
Hi Jeff,
My responses are inline.
On Tue, Jun 26, 2018 at 02:11:46AM +, Jeff Belz wrote:
> All:
>
>
> I'm using a BroadCom(Cypress)43438 Bluetooth chip that receives a 4 wire HCI.
> I got one response that said I just have to change the syscfg setting in my
> target to
>
>
>
>