Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

During the BLE scan, shows Nuttx for you ?

I remember that weeks ago i had seen it...when i was tryng to compile nuttx 
(ble)

Enviado do Email para Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

Hi Matias,

No, it´s referent to an app example, if you some example to access the NIMBLE 
on Nuttx



Enviado do Email para Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Matias N.]

Hi Miguel,

if you have questions regarding using nimBLE I suggest you go to their
support channels as this is really not NuttX related.

Best,
Matias

On Tue, Jun 8, 2021, at 14:01, Miguel Wisintainer wrote:
> Hi Matias

>  

> Have you some example to make the scan ?

>  

> Enviado do Email  para 
> Windows 10

>  

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

Hi Matias

Have you some example to make the scan ?

Enviado do Email para Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

How can i do a scan test ?

Enviado do Email para Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

First experiments on NRF52840

nsh> nimble &
nimble [5:255]
hci init
port init
gap init
gatt init
ans init
ias init
lls init
tps init
hci_sock task init
ble_host task init
nsh> hci sock task
host task

nsh> free
nsh: free: Could not open /proc/meminfo (is procfs mounted?): 2
nsh> mount -t procfs /proc
nsh> free
 total   used   freelargest
Umem:96736  26128  70608  70576
nsh> ps
  PID PRI POLICY   TYPENPX STATEEVENT SIGMASK   STACK COMMAND
0   0 FIFO Kthread N-- Ready   002048 Idle Task
1 224 RR   Kthread --- Waiting  Signal 002032 hpwork
2 100 RR   Kthread --- Waiting  Signal 002032 lpwork
3 100 RR   Task--- Running 002032 init
4 100 RR   Kthread --- Waiting  MQ empty   001000 BT HCI Tx
5 255 RR   Task--- Waiting  Signal 002032 nimble
6   1 RR   pthread --- Waiting  MQ empty   002048 pt-0x128b9 0
7   1 RR   pthread --- Waiting  Semaphore  002048 pt-0x128d1 0
nsh>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Thank you Matias,

I'll do it!

BR,

Alan

On 6/1/21, Matias N.  wrote:
> Sorry, no idea. You should probably enable debugging and see what is
> happening.
>
> Best,
> Matias
>
> On Tue, Jun 1, 2021, at 11:54, Alan Carvalho de Assis wrote:
>> After reducing the stack from 16KB to 2KB I got same result as yours
>> Erik:
>>
>> NuttShell (NSH) NuttX-10.1.0-RC1
>> nsh> nimble &
>> nimble [5:255]
>> hci init
>> port init
>> gap init
>> gatt init
>> ans init
>> ias init
>> lls init
>> tps init
>> hci_sock task init
>> ble_host task init
>> nsh> hci sock task
>> host task
>>
>> nsh> ifconfig
>> bnep0   Link encap:UNSPEC at UP
>>
>> Matias, do you have some idea why we are not seeing the BLE adverting?
>>
>> BR,
>>
>> Alan
>>
>> On 6/1/21, Erik Englund > > wrote:
>> > Change the Nimble stacksize from 16384 to 2048, the nimble application
>> > starts as it should.
>> > Haven't had time to look into it anymore, it should've been 16k for a
>> > reason.
>> >
>> > We´ll have to trim stacksizes to leave some ram for the actual
>> > application
>> > though.
>> >
>> > I guess the board should start advertising some data, which it doesn't.
>> > I´m not familiar with Mynewt/Nimble at all, our BLE products use the
>> > zephyr
>> > rtos/stack together with MCUboot.
>> >
>> >
>> > This is tested on nrf52832-dk.
>> >
>> > apps/wireless/bluetooth/nimble/Makefile
>> > STACKSIZE = 2048
>> >
>> > NuttShell (NSH) NuttX-10.1.0-RC1
>> > nsh> nimble &
>> > nimble [5:255]
>> > hci init
>> > port init
>> > gap init
>> > gatt init
>> > ans init
>> > ias init
>> > lls init
>> > tps init
>> > hci_sock task init
>> > ble_host task init
>> > nsh> hci sock task
>> > host task
>> > free
>> >  total   used   freelargest  nused
>> > nfree
>> > Umem:31120  26144   4976   4944 83
>> > 2
>> > nsh> ps
>> >   PID PRI POLICY   TYPENPX STATEEVENT SIGMASK   STACK
>> > USED
>> >  FILLED COMMAND
>> > 0   0 FIFO Kthread N-- Ready   002048
>> > 000536
>> >  26.1%  Idle Task
>> > 1 224 RR   Kthread --- Waiting  Signal 002032
>> > 000600
>> >  29.5%  hpwork
>> > 2 100 RR   Kthread --- Waiting  Signal 002032
>> > 000600
>> >  29.5%  lpwork
>> > 3 100 RR   Task--- Running 002032
>> > 001308
>> >  64.3%  init
>> > 4 100 RR   Kthread --- Waiting  MQ empty   001000
>> > 000408
>> >  40.8%  BT HCI Tx
>> > 5 255 RR   Task--- Waiting  Signal 002032
>> > 000856
>> >  42.1%  nimble
>> > 6   1 RR   pthread --- Waiting  MQ empty   002048
>> > 000440
>> >  21.4%  pt-0x12bed 0
>> > 7   1 RR   pthread --- Waiting  Semaphore  002048
>> > 000736
>> >  35.9%  pt-0x12c05 0
>> > nsh>
>> >
>> >
>> >  arm-none-eabi-size nuttx
>> >textdata bss dec hex filename
>> >  3135742340   29472  345386   5452a nuttx
>> >
>> > Med vänlig hälsning
>> > Erik Englund
>> >
>> > Innoware Development AB
>> > Hyttvägen 13
>> >
>> > 73338 SALA
>> > Org.nr. 556790-2977
>> > www.innoware.se
>> >
>> >
>> > Den lör 29 maj 2021 kl 01:03 skrev Nathan Hartman
>> > mailto:hartman.nathan%40gmail.com>
>> >>:
>> >
>> >> On Fri, May 28, 2021 at 5:24 PM Alan Carvalho de Assis
>> >> mailto:acassis%40gmail.com>>
>> >> wrote:
>> >>
>> >> > Hi Nathan,
>> >> >
>> >> > On 5/28/21, Nathan Hartman > >> > > wrote:
>> >> > > On Fri, May 28, 2021 at 4:43 PM Alan Carvalho de Assis
>> >> > > mailto:acassis%40gmail.com>> wrote:
>> >> > >>
>> >> > >> Hi Erik,
>> >> > >>
>> >> > >> Thank you very much for your help.
>> >> > >>
>> >> > >> I noticed the final binary is too big (more than 300KB), is it
>> >> > >> also
>> >> > >> happening to you?
>> >> > >>
>> >> > >> BR,
>> >> > >>
>> >> > >> Alan
>> >> > >
>> >> > >
>> >> > > Do some sections in the linker script need (NOLOAD)?
>> >> > >
>> >> > > See PR-3198 [1], where the binary was also huge, until davids5
>> >> > > taught
>> >> > > me about that:
>> >> > >
>> >> > > [1] https://github.com/apache/incubator-nuttx/pull/3198
>> >> > >
>> >> >
>> >> > Good question!
>> >> >
>> >> > When using external libraries with NuttX I need to use
>> >> > "--gc-sections"
>> >> > to reduce the final size:
>> >> >
>> >> >
>> >> >
>> >> https://acassis.wordpress.com/2020/10/06/linking-external-libraries-on-nuttx/
>> >> >
>> >> > BR,
>> >> >
>> >> > Alan
>> >>
>> >>
>> >>
>> >> Ah, yes, I use that too, together with -ffunction-sections and
>> >> -fdata-sections, because the linker gc works at the granularity of a
>> >> section.
>> >>
>> >> Did it work in this case?
>> >>
>> >> Nathan
>> >>
>> >
>>
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

After reducing the stack from 16KB to 2KB I got same result as yours Erik:

NuttShell (NSH) NuttX-10.1.0-RC1
nsh> nimble &
nimble [5:255]
hci init
port init
gap init
gatt init
ans init
ias init
lls init
tps init
hci_sock task init
ble_host task init
nsh> hci sock task
host task

nsh> ifconfig
bnep0   Link encap:UNSPEC at UP

Matias, do you have some idea why we are not seeing the BLE adverting?

BR,

Alan

On 6/1/21, Erik Englund  wrote:
> Change the Nimble stacksize from 16384 to 2048, the nimble application
> starts as it should.
> Haven't had time to look into it anymore, it should've been 16k for a
> reason.
>
> We´ll have to trim stacksizes to leave some ram for the actual application
> though.
>
> I guess the board should start advertising some data, which it doesn't.
> I´m not familiar with Mynewt/Nimble at all, our BLE products use the zephyr
> rtos/stack together with MCUboot.
>
>
> This is tested on nrf52832-dk.
>
> apps/wireless/bluetooth/nimble/Makefile
> STACKSIZE = 2048
>
> NuttShell (NSH) NuttX-10.1.0-RC1
> nsh> nimble &
> nimble [5:255]
> hci init
> port init
> gap init
> gatt init
> ans init
> ias init
> lls init
> tps init
> hci_sock task init
> ble_host task init
> nsh> hci sock task
> host task
> free
>  total   used   freelargest  nused  nfree
> Umem:31120  26144   4976   4944 83  2
> nsh> ps
>   PID PRI POLICY   TYPENPX STATEEVENT SIGMASK   STACK   USED
>  FILLED COMMAND
> 0   0 FIFO Kthread N-- Ready   002048 000536
>  26.1%  Idle Task
> 1 224 RR   Kthread --- Waiting  Signal 002032 000600
>  29.5%  hpwork
> 2 100 RR   Kthread --- Waiting  Signal 002032 000600
>  29.5%  lpwork
> 3 100 RR   Task--- Running 002032 001308
>  64.3%  init
> 4 100 RR   Kthread --- Waiting  MQ empty   001000 000408
>  40.8%  BT HCI Tx
> 5 255 RR   Task--- Waiting  Signal 002032 000856
>  42.1%  nimble
> 6   1 RR   pthread --- Waiting  MQ empty   002048 000440
>  21.4%  pt-0x12bed 0
> 7   1 RR   pthread --- Waiting  Semaphore  002048 000736
>  35.9%  pt-0x12c05 0
> nsh>
>
>
>  arm-none-eabi-size nuttx
>textdata bss dec hex filename
>  3135742340   29472  345386   5452a nuttx
>
> Med vänlig hälsning
> Erik Englund
>
> Innoware Development AB
> Hyttvägen 13
>
> 73338 SALA
> Org.nr. 556790-2977
> www.innoware.se
>
>
> Den lör 29 maj 2021 kl 01:03 skrev Nathan Hartman >:
>
>> On Fri, May 28, 2021 at 5:24 PM Alan Carvalho de Assis
>> 
>> wrote:
>>
>> > Hi Nathan,
>> >
>> > On 5/28/21, Nathan Hartman  wrote:
>> > > On Fri, May 28, 2021 at 4:43 PM Alan Carvalho de Assis
>> > >  wrote:
>> > >>
>> > >> Hi Erik,
>> > >>
>> > >> Thank you very much for your help.
>> > >>
>> > >> I noticed the final binary is too big (more than 300KB), is it also
>> > >> happening to you?
>> > >>
>> > >> BR,
>> > >>
>> > >> Alan
>> > >
>> > >
>> > > Do some sections in the linker script need (NOLOAD)?
>> > >
>> > > See PR-3198 [1], where the binary was also huge, until davids5 taught
>> > > me about that:
>> > >
>> > > [1] https://github.com/apache/incubator-nuttx/pull/3198
>> > >
>> >
>> > Good question!
>> >
>> > When using external libraries with NuttX I need to use "--gc-sections"
>> > to reduce the final size:
>> >
>> >
>> >
>> https://acassis.wordpress.com/2020/10/06/linking-external-libraries-on-nuttx/
>> >
>> > BR,
>> >
>> > Alan
>>
>>
>>
>> Ah, yes, I use that too, together with -ffunction-sections and
>> -fdata-sections, because the linker gc works at the granularity of a
>> section.
>>
>> Did it work in this case?
>>
>> Nathan
>>
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Erik Englund]

Change the Nimble stacksize from 16384 to 2048, the nimble application
starts as it should.
Haven't had time to look into it anymore, it should've been 16k for a
reason.

We´ll have to trim stacksizes to leave some ram for the actual application
though.

I guess the board should start advertising some data, which it doesn't.
I´m not familiar with Mynewt/Nimble at all, our BLE products use the zephyr
rtos/stack together with MCUboot.


This is tested on nrf52832-dk.

apps/wireless/bluetooth/nimble/Makefile
STACKSIZE = 2048

NuttShell (NSH) NuttX-10.1.0-RC1
nsh> nimble &
nimble [5:255]
hci init
port init
gap init
gatt init
ans init
ias init
lls init
tps init
hci_sock task init
ble_host task init
nsh> hci sock task
host task
free
 total   used   freelargest  nused  nfree
Umem:31120  26144   4976   4944 83  2
nsh> ps
  PID PRI POLICY   TYPENPX STATEEVENT SIGMASK   STACK   USED
 FILLED COMMAND
0   0 FIFO Kthread N-- Ready   002048 000536
 26.1%  Idle Task
1 224 RR   Kthread --- Waiting  Signal 002032 000600
 29.5%  hpwork
2 100 RR   Kthread --- Waiting  Signal 002032 000600
 29.5%  lpwork
3 100 RR   Task--- Running 002032 001308
 64.3%  init
4 100 RR   Kthread --- Waiting  MQ empty   001000 000408
 40.8%  BT HCI Tx
5 255 RR   Task--- Waiting  Signal 002032 000856
 42.1%  nimble
6   1 RR   pthread --- Waiting  MQ empty   002048 000440
 21.4%  pt-0x12bed 0
7   1 RR   pthread --- Waiting  Semaphore  002048 000736
 35.9%  pt-0x12c05 0
nsh>


 arm-none-eabi-size nuttx
   textdata bss dec hex filename
 3135742340   29472  345386   5452a nuttx

Med vänlig hälsning
Erik Englund

Innoware Development AB
Hyttvägen 13

73338 SALA
Org.nr. 556790-2977
www.innoware.se


Den lör 29 maj 2021 kl 01:03 skrev Nathan Hartman :

> On Fri, May 28, 2021 at 5:24 PM Alan Carvalho de Assis 
> wrote:
>
> > Hi Nathan,
> >
> > On 5/28/21, Nathan Hartman  wrote:
> > > On Fri, May 28, 2021 at 4:43 PM Alan Carvalho de Assis
> > >  wrote:
> > >>
> > >> Hi Erik,
> > >>
> > >> Thank you very much for your help.
> > >>
> > >> I noticed the final binary is too big (more than 300KB), is it also
> > >> happening to you?
> > >>
> > >> BR,
> > >>
> > >> Alan
> > >
> > >
> > > Do some sections in the linker script need (NOLOAD)?
> > >
> > > See PR-3198 [1], where the binary was also huge, until davids5 taught
> > > me about that:
> > >
> > > [1] https://github.com/apache/incubator-nuttx/pull/3198
> > >
> >
> > Good question!
> >
> > When using external libraries with NuttX I need to use "--gc-sections"
> > to reduce the final size:
> >
> >
> >
> https://acassis.wordpress.com/2020/10/06/linking-external-libraries-on-nuttx/
> >
> > BR,
> >
> > Alan
>
>
>
> Ah, yes, I use that too, together with -ffunction-sections and
> -fdata-sections, because the linker gc works at the granularity of a
> section.
>
> Did it work in this case?
>
> Nathan
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Hi Miguel,

the size text font in the image you sent is impossible to read.

I suggest you to select the text and post it here as raw text instead
attaching image.

BR,

Alan

On 5/29/21, Miguel Wisintainer  wrote:
> Some questions,
> I can see the nimble and i can execute, but freeze...must it to be execute
> with &
> I can see too the bnep0
> Wich app and sintax to test it ?
>
> [cid:image002.png@01D754A2.25216660]
> Enviado do Email para
> Windows 10
>
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

Some questions,
I can see the nimble and i can execute, but freeze...must it to be execute with 
&
I can see too the bnep0
Wich app and sintax to test it ?

[cid:image002.png@01D754A2.25216660]
Enviado do Email para Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Nathan Hartman]

On Fri, May 28, 2021 at 5:24 PM Alan Carvalho de Assis 
wrote:

> Hi Nathan,
>
> On 5/28/21, Nathan Hartman  wrote:
> > On Fri, May 28, 2021 at 4:43 PM Alan Carvalho de Assis
> >  wrote:
> >>
> >> Hi Erik,
> >>
> >> Thank you very much for your help.
> >>
> >> I noticed the final binary is too big (more than 300KB), is it also
> >> happening to you?
> >>
> >> BR,
> >>
> >> Alan
> >
> >
> > Do some sections in the linker script need (NOLOAD)?
> >
> > See PR-3198 [1], where the binary was also huge, until davids5 taught
> > me about that:
> >
> > [1] https://github.com/apache/incubator-nuttx/pull/3198
> >
>
> Good question!
>
> When using external libraries with NuttX I need to use "--gc-sections"
> to reduce the final size:
>
>
> https://acassis.wordpress.com/2020/10/06/linking-external-libraries-on-nuttx/
>
> BR,
>
> Alan



Ah, yes, I use that too, together with -ffunction-sections and
-fdata-sections, because the linker gc works at the granularity of a
section.

Did it work in this case?

Nathan

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Hi Nathan,

On 5/28/21, Nathan Hartman  wrote:
> On Fri, May 28, 2021 at 4:43 PM Alan Carvalho de Assis
>  wrote:
>>
>> Hi Erik,
>>
>> Thank you very much for your help.
>>
>> I noticed the final binary is too big (more than 300KB), is it also
>> happening to you?
>>
>> BR,
>>
>> Alan
>
>
> Do some sections in the linker script need (NOLOAD)?
>
> See PR-3198 [1], where the binary was also huge, until davids5 taught
> me about that:
>
> [1] https://github.com/apache/incubator-nuttx/pull/3198
>

Good question!

When using external libraries with NuttX I need to use "--gc-sections"
to reduce the final size:

https://acassis.wordpress.com/2020/10/06/linking-external-libraries-on-nuttx/

BR,

Alan

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Hi Erik,

Thank you very much for your help.

I noticed the final binary is too big (more than 300KB), is it also
happening to you?

BR,

Alan

On 5/27/21, Erik Englund  wrote:
> Yes, I think seamless Nordic BLE support is important for NuttX.
>
> I will try to release some time for this, I´ve got nrf52832, nrf52833 and
> nrf52840 boards/products at my disposal.
>
> Med vänlig hälsning
> Erik Englund
>
> Innoware Development AB
> Hyttvägen 13
> 73338 SALA
>
> Org.nr. 556790-2977
> www.innoware.se
>
>
> Den ons 26 maj 2021 kl 11:42 skrev Alan Carvalho de Assis
> >:
>
>> Thank you Erik and Greg,
>>
>> I think we need to modify the default "sdc" board config to get nimBLE
>> running correctly.
>>
>> Thank you for these suggestions.
>>
>> BR,
>>
>> Alan
>>
>> On Wednesday, May 26, 2021, Erik Englund 
>> wrote:
>>
>> > I was encountering the same error while trying to run NuttX 10.x /
>> > nimble
>> > on NRF52832, tracked it down to insufficient ram available.
>> > The nimble nsh-app were present in the builtin-apps internal lists, but
>> > when trying to allocate application stack NuttX will return an error
>> code,
>> > and it seems all allocation error codes when trying to start an nsh-app
>> > will result in that "command not found" error message.
>> > I think enabling some memory debugging flags in nuttx will show you the
>> > correct error.
>> >
>> > So this isn't a nimble problem.
>> >
>> >
>> > Med vänlig hälsning
>> > Erik Englund
>> >
>> > Innoware Development AB
>> > Hyttvägen 13
>> > 73338 SALA
>> >
>> >
>> > Org.nr. 556790-2977
>> > www.innoware.se
>> >
>> >
>> > Den ons 26 maj 2021 kl 01:42 skrev Gregory Nutt :
>> >
>> > > The failure doesn't seem to have anything to do with nimBLE.  The
>> nimble
>> > > app is not running at all!
>> > >
>> > > Put a breakpoint on nimble_main().  I doubt that you ever get there.
>> > > But I don't know why.
>> > >
>> > > The error report is probably misleading too...  I seem to recall that
>> > > that there is an issue that the NSH error reported is always "command
>> > > not found" even if some other error occurs.  It does mean that NSH
>> could
>> > > not run the built-in command, but it does not necessarily mean that
>> > > the
>> > > built-in command was not found.
>> > >
>> > > On 5/25/2021 4:51 PM, Alan Carvalho de Assis wrote:
>> > > > Hi Matias and Miguel,
>> > > >
>> > > > I just tried nimble on nrf52832-mdk board without success:
>> > > >
>> > > > $ ./tools/configure.sh nrf52832-mdk:sdc
>> > > > $ make
>> > > >
>> > > > It downloaded and compiled nimble for NuttX correctly, the
>> > > > nuttx.bin
>> > > > was about 314944 bytes.
>> > > >
>> > > > When I drop this file inside DAPLINK disk it tries to flash and
>> create
>> > > > the file FAIL.TXT with this content:
>> > > >
>> > > > "The hex file cannot be decoded. Checksum calculation failure
>> > occurred."
>> > > >
>> > > > Then I ran "make menuconfig" and enabled the "Intel HEX binary
>> format"
>> > > > and after copying the nuttx.hex to DAPLINK disk the error
>> disappeared.
>> > > >
>> > > > Accessing the nsh terminal I can see the nimble binary, but it is
>> > > > not
>> > > running:
>> > > >
>> > > > NuttShell (NSH) NuttX-10.1.0-RC1
>> > > > nsh> ?
>> > > > help usage:  help [-v] []
>> > > >
>> > > >. cdecho  hexdump   mkdir ps
>> > > > source
>> > > >   unset
>> > > >[ cpexec  ifconfig  mkfatfs   pwd   test
>> > > >   usleep
>> > > >? cmp   exit  ifdownmkrd  rmtime
>> > > >   xd
>> > > >basename  dirname   false ifup  mount rmdir true
>> > > >break ddfree  kill  mvset
>> > > > uname
>> > > >cat   dfhelp  lsnslookup  sleep
>> > > > umount
>> > > >
>> > > > Builtin Apps:
>> > > >nimble  sh  nsh
>> > > > nsh> nimble
>> > > > nsh: nimble: command not found
>> > > > nsh> ifconfig
>> > > > bnep0   Link encap:UNSPEC at UP
>> > > >
>> > > > nsh> nimble -h
>> > > > nsh: nimble: command not found
>> > > > nsh> nimble
>> > > > nsh: nimble: command not found
>> > > > nsh>
>> > > >
>> > > > Initially I thought it was caused by recent update of the nimble
>> stack
>> > > > on NuttX, but I moved to a commit previous to that update and still
>> > > > facing same error.
>> > > >
>> > > > Matias, do you think it could be some issue with my crosscompiler?
>> > > >
>> > > > I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi
>> > > package:
>> > > >
>> > > > gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
>> > > > 277599] (15:9-2019-q4-0ubuntu1)
>> > > >
>> > > > Thank you very much!
>> > > >
>> > > > BR,
>> > > >
>> > > > Alan
>> > > >
>> > > > On 5/25/21, Miguel Wisintainer  wrote:
>> > > >> Matias
>> > > >>
>> > > >> Me and Alan will investigate!
>> > > >>
>> > > >> Thank you so much!
>> > > >>
>> > > >> Enviado do Email
>> para
>> > > >> Windows 10
>> > > 

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Erik Englund]

Yes, I think seamless Nordic BLE support is important for NuttX.

I will try to release some time for this, I´ve got nrf52832, nrf52833 and
nrf52840 boards/products at my disposal.

Med vänlig hälsning
Erik Englund

Innoware Development AB
Hyttvägen 13
73338 SALA

Org.nr. 556790-2977
www.innoware.se


Den ons 26 maj 2021 kl 11:42 skrev Alan Carvalho de Assis :

> Thank you Erik and Greg,
>
> I think we need to modify the default "sdc" board config to get nimBLE
> running correctly.
>
> Thank you for these suggestions.
>
> BR,
>
> Alan
>
> On Wednesday, May 26, 2021, Erik Englund  wrote:
>
> > I was encountering the same error while trying to run NuttX 10.x / nimble
> > on NRF52832, tracked it down to insufficient ram available.
> > The nimble nsh-app were present in the builtin-apps internal lists, but
> > when trying to allocate application stack NuttX will return an error
> code,
> > and it seems all allocation error codes when trying to start an nsh-app
> > will result in that "command not found" error message.
> > I think enabling some memory debugging flags in nuttx will show you the
> > correct error.
> >
> > So this isn't a nimble problem.
> >
> >
> > Med vänlig hälsning
> > Erik Englund
> >
> > Innoware Development AB
> > Hyttvägen 13
> > 73338 SALA
> >
> >
> > Org.nr. 556790-2977
> > www.innoware.se
> >
> >
> > Den ons 26 maj 2021 kl 01:42 skrev Gregory Nutt :
> >
> > > The failure doesn't seem to have anything to do with nimBLE.  The
> nimble
> > > app is not running at all!
> > >
> > > Put a breakpoint on nimble_main().  I doubt that you ever get there.
> > > But I don't know why.
> > >
> > > The error report is probably misleading too...  I seem to recall that
> > > that there is an issue that the NSH error reported is always "command
> > > not found" even if some other error occurs.  It does mean that NSH
> could
> > > not run the built-in command, but it does not necessarily mean that the
> > > built-in command was not found.
> > >
> > > On 5/25/2021 4:51 PM, Alan Carvalho de Assis wrote:
> > > > Hi Matias and Miguel,
> > > >
> > > > I just tried nimble on nrf52832-mdk board without success:
> > > >
> > > > $ ./tools/configure.sh nrf52832-mdk:sdc
> > > > $ make
> > > >
> > > > It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
> > > > was about 314944 bytes.
> > > >
> > > > When I drop this file inside DAPLINK disk it tries to flash and
> create
> > > > the file FAIL.TXT with this content:
> > > >
> > > > "The hex file cannot be decoded. Checksum calculation failure
> > occurred."
> > > >
> > > > Then I ran "make menuconfig" and enabled the "Intel HEX binary
> format"
> > > > and after copying the nuttx.hex to DAPLINK disk the error
> disappeared.
> > > >
> > > > Accessing the nsh terminal I can see the nimble binary, but it is not
> > > running:
> > > >
> > > > NuttShell (NSH) NuttX-10.1.0-RC1
> > > > nsh> ?
> > > > help usage:  help [-v] []
> > > >
> > > >. cdecho  hexdump   mkdir pssource
> > > >   unset
> > > >[ cpexec  ifconfig  mkfatfs   pwd   test
> > > >   usleep
> > > >? cmp   exit  ifdownmkrd  rmtime
> > > >   xd
> > > >basename  dirname   false ifup  mount rmdir true
> > > >break ddfree  kill  mvset   uname
> > > >cat   dfhelp  lsnslookup  sleep umount
> > > >
> > > > Builtin Apps:
> > > >nimble  sh  nsh
> > > > nsh> nimble
> > > > nsh: nimble: command not found
> > > > nsh> ifconfig
> > > > bnep0   Link encap:UNSPEC at UP
> > > >
> > > > nsh> nimble -h
> > > > nsh: nimble: command not found
> > > > nsh> nimble
> > > > nsh: nimble: command not found
> > > > nsh>
> > > >
> > > > Initially I thought it was caused by recent update of the nimble
> stack
> > > > on NuttX, but I moved to a commit previous to that update and still
> > > > facing same error.
> > > >
> > > > Matias, do you think it could be some issue with my crosscompiler?
> > > >
> > > > I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi
> > > package:
> > > >
> > > > gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
> > > > 277599] (15:9-2019-q4-0ubuntu1)
> > > >
> > > > Thank you very much!
> > > >
> > > > BR,
> > > >
> > > > Alan
> > > >
> > > > On 5/25/21, Miguel Wisintainer  wrote:
> > > >> Matias
> > > >>
> > > >> Me and Alan will investigate!
> > > >>
> > > >> Thank you so much!
> > > >>
> > > >> Enviado do Email
> para
> > > >> Windows 10
> > > >>
> > > >>
> > >
> >
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Thank you Erik and Greg,

I think we need to modify the default "sdc" board config to get nimBLE
running correctly.

Thank you for these suggestions.

BR,

Alan

On Wednesday, May 26, 2021, Erik Englund  wrote:

> I was encountering the same error while trying to run NuttX 10.x / nimble
> on NRF52832, tracked it down to insufficient ram available.
> The nimble nsh-app were present in the builtin-apps internal lists, but
> when trying to allocate application stack NuttX will return an error code,
> and it seems all allocation error codes when trying to start an nsh-app
> will result in that "command not found" error message.
> I think enabling some memory debugging flags in nuttx will show you the
> correct error.
>
> So this isn't a nimble problem.
>
>
> Med vänlig hälsning
> Erik Englund
>
> Innoware Development AB
> Hyttvägen 13
> 73338 SALA
>
>
> Org.nr. 556790-2977
> www.innoware.se
>
>
> Den ons 26 maj 2021 kl 01:42 skrev Gregory Nutt :
>
> > The failure doesn't seem to have anything to do with nimBLE.  The nimble
> > app is not running at all!
> >
> > Put a breakpoint on nimble_main().  I doubt that you ever get there.
> > But I don't know why.
> >
> > The error report is probably misleading too...  I seem to recall that
> > that there is an issue that the NSH error reported is always "command
> > not found" even if some other error occurs.  It does mean that NSH could
> > not run the built-in command, but it does not necessarily mean that the
> > built-in command was not found.
> >
> > On 5/25/2021 4:51 PM, Alan Carvalho de Assis wrote:
> > > Hi Matias and Miguel,
> > >
> > > I just tried nimble on nrf52832-mdk board without success:
> > >
> > > $ ./tools/configure.sh nrf52832-mdk:sdc
> > > $ make
> > >
> > > It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
> > > was about 314944 bytes.
> > >
> > > When I drop this file inside DAPLINK disk it tries to flash and create
> > > the file FAIL.TXT with this content:
> > >
> > > "The hex file cannot be decoded. Checksum calculation failure
> occurred."
> > >
> > > Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
> > > and after copying the nuttx.hex to DAPLINK disk the error disappeared.
> > >
> > > Accessing the nsh terminal I can see the nimble binary, but it is not
> > running:
> > >
> > > NuttShell (NSH) NuttX-10.1.0-RC1
> > > nsh> ?
> > > help usage:  help [-v] []
> > >
> > >. cdecho  hexdump   mkdir pssource
> > >   unset
> > >[ cpexec  ifconfig  mkfatfs   pwd   test
> > >   usleep
> > >? cmp   exit  ifdownmkrd  rmtime
> > >   xd
> > >basename  dirname   false ifup  mount rmdir true
> > >break ddfree  kill  mvset   uname
> > >cat   dfhelp  lsnslookup  sleep umount
> > >
> > > Builtin Apps:
> > >nimble  sh  nsh
> > > nsh> nimble
> > > nsh: nimble: command not found
> > > nsh> ifconfig
> > > bnep0   Link encap:UNSPEC at UP
> > >
> > > nsh> nimble -h
> > > nsh: nimble: command not found
> > > nsh> nimble
> > > nsh: nimble: command not found
> > > nsh>
> > >
> > > Initially I thought it was caused by recent update of the nimble stack
> > > on NuttX, but I moved to a commit previous to that update and still
> > > facing same error.
> > >
> > > Matias, do you think it could be some issue with my crosscompiler?
> > >
> > > I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi
> > package:
> > >
> > > gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
> > > 277599] (15:9-2019-q4-0ubuntu1)
> > >
> > > Thank you very much!
> > >
> > > BR,
> > >
> > > Alan
> > >
> > > On 5/25/21, Miguel Wisintainer  wrote:
> > >> Matias
> > >>
> > >> Me and Alan will investigate!
> > >>
> > >> Thank you so much!
> > >>
> > >> Enviado do Email para
> > >> Windows 10
> > >>
> > >>
> >
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Erik Englund]

I was encountering the same error while trying to run NuttX 10.x / nimble
on NRF52832, tracked it down to insufficient ram available.
The nimble nsh-app were present in the builtin-apps internal lists, but
when trying to allocate application stack NuttX will return an error code,
and it seems all allocation error codes when trying to start an nsh-app
will result in that "command not found" error message.
I think enabling some memory debugging flags in nuttx will show you the
correct error.

So this isn't a nimble problem.


Med vänlig hälsning
Erik Englund

Innoware Development AB
Hyttvägen 13
73338 SALA


Org.nr. 556790-2977
www.innoware.se


Den ons 26 maj 2021 kl 01:42 skrev Gregory Nutt :

> The failure doesn't seem to have anything to do with nimBLE.  The nimble
> app is not running at all!
>
> Put a breakpoint on nimble_main().  I doubt that you ever get there.
> But I don't know why.
>
> The error report is probably misleading too...  I seem to recall that
> that there is an issue that the NSH error reported is always "command
> not found" even if some other error occurs.  It does mean that NSH could
> not run the built-in command, but it does not necessarily mean that the
> built-in command was not found.
>
> On 5/25/2021 4:51 PM, Alan Carvalho de Assis wrote:
> > Hi Matias and Miguel,
> >
> > I just tried nimble on nrf52832-mdk board without success:
> >
> > $ ./tools/configure.sh nrf52832-mdk:sdc
> > $ make
> >
> > It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
> > was about 314944 bytes.
> >
> > When I drop this file inside DAPLINK disk it tries to flash and create
> > the file FAIL.TXT with this content:
> >
> > "The hex file cannot be decoded. Checksum calculation failure occurred."
> >
> > Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
> > and after copying the nuttx.hex to DAPLINK disk the error disappeared.
> >
> > Accessing the nsh terminal I can see the nimble binary, but it is not
> running:
> >
> > NuttShell (NSH) NuttX-10.1.0-RC1
> > nsh> ?
> > help usage:  help [-v] []
> >
> >. cdecho  hexdump   mkdir pssource
> >   unset
> >[ cpexec  ifconfig  mkfatfs   pwd   test
> >   usleep
> >? cmp   exit  ifdownmkrd  rmtime
> >   xd
> >basename  dirname   false ifup  mount rmdir true
> >break ddfree  kill  mvset   uname
> >cat   dfhelp  lsnslookup  sleep umount
> >
> > Builtin Apps:
> >nimble  sh  nsh
> > nsh> nimble
> > nsh: nimble: command not found
> > nsh> ifconfig
> > bnep0   Link encap:UNSPEC at UP
> >
> > nsh> nimble -h
> > nsh: nimble: command not found
> > nsh> nimble
> > nsh: nimble: command not found
> > nsh>
> >
> > Initially I thought it was caused by recent update of the nimble stack
> > on NuttX, but I moved to a commit previous to that update and still
> > facing same error.
> >
> > Matias, do you think it could be some issue with my crosscompiler?
> >
> > I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi
> package:
> >
> > gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
> > 277599] (15:9-2019-q4-0ubuntu1)
> >
> > Thank you very much!
> >
> > BR,
> >
> > Alan
> >
> > On 5/25/21, Miguel Wisintainer  wrote:
> >> Matias
> >>
> >> Me and Alan will investigate!
> >>
> >> Thank you so much!
> >>
> >> Enviado do Email para
> >> Windows 10
> >>
> >>
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Gregory Nutt]

The failure doesn't seem to have anything to do with nimBLE.  The nimble 
app is not running at all!


Put a breakpoint on nimble_main().  I doubt that you ever get there.  
But I don't know why.


The error report is probably misleading too...  I seem to recall that 
that there is an issue that the NSH error reported is always "command 
not found" even if some other error occurs.  It does mean that NSH could 
not run the built-in command, but it does not necessarily mean that the 
built-in command was not found.


On 5/25/2021 4:51 PM, Alan Carvalho de Assis wrote:

Hi Matias and Miguel,

I just tried nimble on nrf52832-mdk board without success:

$ ./tools/configure.sh nrf52832-mdk:sdc
$ make

It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
was about 314944 bytes.

When I drop this file inside DAPLINK disk it tries to flash and create
the file FAIL.TXT with this content:

"The hex file cannot be decoded. Checksum calculation failure occurred."

Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
and after copying the nuttx.hex to DAPLINK disk the error disappeared.

Accessing the nsh terminal I can see the nimble binary, but it is not running:

NuttShell (NSH) NuttX-10.1.0-RC1
nsh> ?
help usage:  help [-v] []

   . cdecho  hexdump   mkdir pssource
  unset
   [ cpexec  ifconfig  mkfatfs   pwd   test
  usleep
   ? cmp   exit  ifdownmkrd  rmtime
  xd
   basename  dirname   false ifup  mount rmdir true
   break ddfree  kill  mvset   uname
   cat   dfhelp  lsnslookup  sleep umount

Builtin Apps:
   nimble  sh  nsh
nsh> nimble
nsh: nimble: command not found
nsh> ifconfig
bnep0   Link encap:UNSPEC at UP

nsh> nimble -h
nsh: nimble: command not found
nsh> nimble
nsh: nimble: command not found
nsh>

Initially I thought it was caused by recent update of the nimble stack
on NuttX, but I moved to a commit previous to that update and still
facing same error.

Matias, do you think it could be some issue with my crosscompiler?

I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi package:

gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
277599] (15:9-2019-q4-0ubuntu1)

Thank you very much!

BR,

Alan

On 5/25/21, Miguel Wisintainer  wrote:

Matias

Me and Alan will investigate!

Thank you so much!

Enviado do Email para
Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Seams specific to nimble:

NuttShell (NSH) NuttX-10.1.0-RC1
nsh> ?
help usage:  help [-v] []

  . cdecho  hexdump   mkdir pssource
 unset
  [ cpexec  ifconfig  mkfatfs   pwd   test
 usleep
  ? cmp   exit  ifdownmkrd  rmtime
 xd
  basename  dirname   false ifup  mount rmdir true
  break ddfree  kill  mvset   uname
  cat   dfhelp  lsnslookup  sleep umount

Builtin Apps:
  nimble  sh  hello   nsh
nsh> nimble
nsh: nimble: command not found
nsh> hello
Hello, World!!
nsh> ifconfig
bnep0   Link encap:UNSPEC at UP

nsh>



On 5/25/21, Matias N.  wrote:
> I can try tomorrow. Maybe you can try enabling another app and see if you
> can run it. The "command not found" seems unrelated to nimBLE.
>
> On Tue, May 25, 2021, at 20:26, Alan Carvalho de Assis wrote:
>> Hi Matias,
>>
>> No, this is not the issue:
>>
>> Symbol: BUILTIN [=y]
>> Symbol: NSH_BUILTIN_APPS [=y]
>>
>> As you saw I used your "nrf52832-mdk:sdc" and you enabled it there.
>>
>> Is it working for you?
>>
>> BR,
>>
>> Alan
>>
>> On 5/25/21, Matias N. mailto:matias%40imap.cc>> wrote:
>> > The problem with apps listed but not being able to run them is a common
>> > error (something worth adding
>> > to the FAQ) I faced many times. It is due to not having support for
>> > BUILTIN
>> > apps on menuconfig (you need general
>> > support as well as enabling NSH BUILTIN support). It is strange that
>> > the
>> > config is not functional though.
>> >
>> > Best,
>> > Matias
>> >
>> > On Tue, May 25, 2021, at 19:51, Alan Carvalho de Assis wrote:
>> >> Hi Matias and Miguel,
>> >>
>> >> I just tried nimble on nrf52832-mdk board without success:
>> >>
>> >> $ ./tools/configure.sh nrf52832-mdk:sdc
>> >> $ make
>> >>
>> >> It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
>> >> was about 314944 bytes.
>> >>
>> >> When I drop this file inside DAPLINK disk it tries to flash and create
>> >> the file FAIL.TXT with this content:
>> >>
>> >> "The hex file cannot be decoded. Checksum calculation failure
>> >> occurred."
>> >>
>> >> Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
>> >> and after copying the nuttx.hex to DAPLINK disk the error disappeared.
>> >>
>> >> Accessing the nsh terminal I can see the nimble binary, but it is not
>> >> running:
>> >>
>> >> NuttShell (NSH) NuttX-10.1.0-RC1
>> >> nsh> ?
>> >> help usage:  help [-v] []
>> >>
>> >>   . cdecho  hexdump   mkdir pssource
>> >> unset
>> >>   [ cpexec  ifconfig  mkfatfs   pwd   test
>> >> usleep
>> >>   ? cmp   exit  ifdownmkrd  rmtime
>> >> xd
>> >>   basename  dirname   false ifup  mount rmdir true
>> >>   break ddfree  kill  mvset   uname
>> >>   cat   dfhelp  lsnslookup  sleep umount
>> >>
>> >> Builtin Apps:
>> >>   nimble  sh  nsh
>> >> nsh> nimble
>> >> nsh: nimble: command not found
>> >> nsh> ifconfig
>> >> bnep0   Link encap:UNSPEC at UP
>> >>
>> >> nsh> nimble -h
>> >> nsh: nimble: command not found
>> >> nsh> nimble
>> >> nsh: nimble: command not found
>> >> nsh>
>> >>
>> >> Initially I thought it was caused by recent update of the nimble stack
>> >> on NuttX, but I moved to a commit previous to that update and still
>> >> facing same error.
>> >>
>> >> Matias, do you think it could be some issue with my crosscompiler?
>> >>
>> >> I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi
>> >> package:
>> >>
>> >> gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
>> >> 277599] (15:9-2019-q4-0ubuntu1)
>> >>
>> >> Thank you very much!
>> >>
>> >> BR,
>> >>
>> >> Alan
>> >>
>> >> On 5/25/21, Miguel Wisintainer > >> 
>> >> > wrote:
>> >> > Matias
>> >> >
>> >> > Me and Alan will investigate!
>> >> >
>> >> > Thank you so much!
>> >> >
>> >> > Enviado do Email
>> >> > para
>> >> > Windows 10
>> >> >
>> >> >
>> >>
>> >
>>
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Matias N.]

I can try tomorrow. Maybe you can try enabling another app and see if you can 
run it. The "command not found" seems unrelated to nimBLE.

On Tue, May 25, 2021, at 20:26, Alan Carvalho de Assis wrote:
> Hi Matias,
> 
> No, this is not the issue:
> 
> Symbol: BUILTIN [=y]
> Symbol: NSH_BUILTIN_APPS [=y]
> 
> As you saw I used your "nrf52832-mdk:sdc" and you enabled it there.
> 
> Is it working for you?
> 
> BR,
> 
> Alan
> 
> On 5/25/21, Matias N. mailto:matias%40imap.cc>> wrote:
> > The problem with apps listed but not being able to run them is a common
> > error (something worth adding
> > to the FAQ) I faced many times. It is due to not having support for BUILTIN
> > apps on menuconfig (you need general
> > support as well as enabling NSH BUILTIN support). It is strange that the
> > config is not functional though.
> >
> > Best,
> > Matias
> >
> > On Tue, May 25, 2021, at 19:51, Alan Carvalho de Assis wrote:
> >> Hi Matias and Miguel,
> >>
> >> I just tried nimble on nrf52832-mdk board without success:
> >>
> >> $ ./tools/configure.sh nrf52832-mdk:sdc
> >> $ make
> >>
> >> It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
> >> was about 314944 bytes.
> >>
> >> When I drop this file inside DAPLINK disk it tries to flash and create
> >> the file FAIL.TXT with this content:
> >>
> >> "The hex file cannot be decoded. Checksum calculation failure occurred."
> >>
> >> Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
> >> and after copying the nuttx.hex to DAPLINK disk the error disappeared.
> >>
> >> Accessing the nsh terminal I can see the nimble binary, but it is not
> >> running:
> >>
> >> NuttShell (NSH) NuttX-10.1.0-RC1
> >> nsh> ?
> >> help usage:  help [-v] []
> >>
> >>   . cdecho  hexdump   mkdir pssource
> >> unset
> >>   [ cpexec  ifconfig  mkfatfs   pwd   test
> >> usleep
> >>   ? cmp   exit  ifdownmkrd  rmtime
> >> xd
> >>   basename  dirname   false ifup  mount rmdir true
> >>   break ddfree  kill  mvset   uname
> >>   cat   dfhelp  lsnslookup  sleep umount
> >>
> >> Builtin Apps:
> >>   nimble  sh  nsh
> >> nsh> nimble
> >> nsh: nimble: command not found
> >> nsh> ifconfig
> >> bnep0   Link encap:UNSPEC at UP
> >>
> >> nsh> nimble -h
> >> nsh: nimble: command not found
> >> nsh> nimble
> >> nsh: nimble: command not found
> >> nsh>
> >>
> >> Initially I thought it was caused by recent update of the nimble stack
> >> on NuttX, but I moved to a commit previous to that update and still
> >> facing same error.
> >>
> >> Matias, do you think it could be some issue with my crosscompiler?
> >>
> >> I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi
> >> package:
> >>
> >> gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
> >> 277599] (15:9-2019-q4-0ubuntu1)
> >>
> >> Thank you very much!
> >>
> >> BR,
> >>
> >> Alan
> >>
> >> On 5/25/21, Miguel Wisintainer  >> 
> >> > wrote:
> >> > Matias
> >> >
> >> > Me and Alan will investigate!
> >> >
> >> > Thank you so much!
> >> >
> >> > Enviado do Email para
> >> > Windows 10
> >> >
> >> >
> >>
> >
> 

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Hi Matias,

No, this is not the issue:

Symbol: BUILTIN [=y]
Symbol: NSH_BUILTIN_APPS [=y]

As you saw I used your "nrf52832-mdk:sdc" and you enabled it there.

Is it working for you?

BR,

Alan

On 5/25/21, Matias N.  wrote:
> The problem with apps listed but not being able to run them is a common
> error (something worth adding
> to the FAQ) I faced many times. It is due to not having support for BUILTIN
> apps on menuconfig (you need general
> support as well as enabling NSH BUILTIN support). It is strange that the
> config is not functional though.
>
> Best,
> Matias
>
> On Tue, May 25, 2021, at 19:51, Alan Carvalho de Assis wrote:
>> Hi Matias and Miguel,
>>
>> I just tried nimble on nrf52832-mdk board without success:
>>
>> $ ./tools/configure.sh nrf52832-mdk:sdc
>> $ make
>>
>> It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
>> was about 314944 bytes.
>>
>> When I drop this file inside DAPLINK disk it tries to flash and create
>> the file FAIL.TXT with this content:
>>
>> "The hex file cannot be decoded. Checksum calculation failure occurred."
>>
>> Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
>> and after copying the nuttx.hex to DAPLINK disk the error disappeared.
>>
>> Accessing the nsh terminal I can see the nimble binary, but it is not
>> running:
>>
>> NuttShell (NSH) NuttX-10.1.0-RC1
>> nsh> ?
>> help usage:  help [-v] []
>>
>>   . cdecho  hexdump   mkdir pssource
>> unset
>>   [ cpexec  ifconfig  mkfatfs   pwd   test
>> usleep
>>   ? cmp   exit  ifdownmkrd  rmtime
>> xd
>>   basename  dirname   false ifup  mount rmdir true
>>   break ddfree  kill  mvset   uname
>>   cat   dfhelp  lsnslookup  sleep umount
>>
>> Builtin Apps:
>>   nimble  sh  nsh
>> nsh> nimble
>> nsh: nimble: command not found
>> nsh> ifconfig
>> bnep0   Link encap:UNSPEC at UP
>>
>> nsh> nimble -h
>> nsh: nimble: command not found
>> nsh> nimble
>> nsh: nimble: command not found
>> nsh>
>>
>> Initially I thought it was caused by recent update of the nimble stack
>> on NuttX, but I moved to a commit previous to that update and still
>> facing same error.
>>
>> Matias, do you think it could be some issue with my crosscompiler?
>>
>> I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi
>> package:
>>
>> gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
>> 277599] (15:9-2019-q4-0ubuntu1)
>>
>> Thank you very much!
>>
>> BR,
>>
>> Alan
>>
>> On 5/25/21, Miguel Wisintainer > > wrote:
>> > Matias
>> >
>> > Me and Alan will investigate!
>> >
>> > Thank you so much!
>> >
>> > Enviado do Email para
>> > Windows 10
>> >
>> >
>>
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Matias N.]

The problem with apps listed but not being able to run them is a common error 
(something worth adding
to the FAQ) I faced many times. It is due to not having support for BUILTIN 
apps on menuconfig (you need general
support as well as enabling NSH BUILTIN support). It is strange that the config 
is not functional though.

Best,
Matias

On Tue, May 25, 2021, at 19:51, Alan Carvalho de Assis wrote:
> Hi Matias and Miguel,
> 
> I just tried nimble on nrf52832-mdk board without success:
> 
> $ ./tools/configure.sh nrf52832-mdk:sdc
> $ make
> 
> It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
> was about 314944 bytes.
> 
> When I drop this file inside DAPLINK disk it tries to flash and create
> the file FAIL.TXT with this content:
> 
> "The hex file cannot be decoded. Checksum calculation failure occurred."
> 
> Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
> and after copying the nuttx.hex to DAPLINK disk the error disappeared.
> 
> Accessing the nsh terminal I can see the nimble binary, but it is not running:
> 
> NuttShell (NSH) NuttX-10.1.0-RC1
> nsh> ?
> help usage:  help [-v] []
> 
>   . cdecho  hexdump   mkdir pssource
> unset
>   [ cpexec  ifconfig  mkfatfs   pwd   test
> usleep
>   ? cmp   exit  ifdownmkrd  rmtime
> xd
>   basename  dirname   false ifup  mount rmdir true
>   break ddfree  kill  mvset   uname
>   cat   dfhelp  lsnslookup  sleep umount
> 
> Builtin Apps:
>   nimble  sh  nsh
> nsh> nimble
> nsh: nimble: command not found
> nsh> ifconfig
> bnep0   Link encap:UNSPEC at UP
> 
> nsh> nimble -h
> nsh: nimble: command not found
> nsh> nimble
> nsh: nimble: command not found
> nsh>
> 
> Initially I thought it was caused by recent update of the nimble stack
> on NuttX, but I moved to a commit previous to that update and still
> facing same error.
> 
> Matias, do you think it could be some issue with my crosscompiler?
> 
> I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi package:
> 
> gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
> 277599] (15:9-2019-q4-0ubuntu1)
> 
> Thank you very much!
> 
> BR,
> 
> Alan
> 
> On 5/25/21, Miguel Wisintainer  > wrote:
> > Matias
> >
> > Me and Alan will investigate!
> >
> > Thank you so much!
> >
> > Enviado do Email para
> > Windows 10
> >
> >
> 

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Hi Matias and Miguel,

I just tried nimble on nrf52832-mdk board without success:

$ ./tools/configure.sh nrf52832-mdk:sdc
$ make

It downloaded and compiled nimble for NuttX correctly, the nuttx.bin
was about 314944 bytes.

When I drop this file inside DAPLINK disk it tries to flash and create
the file FAIL.TXT with this content:

"The hex file cannot be decoded. Checksum calculation failure occurred."

Then I ran "make menuconfig" and enabled the "Intel HEX binary format"
and after copying the nuttx.hex to DAPLINK disk the error disappeared.

Accessing the nsh terminal I can see the nimble binary, but it is not running:

NuttShell (NSH) NuttX-10.1.0-RC1
nsh> ?
help usage:  help [-v] []

  . cdecho  hexdump   mkdir pssource
 unset
  [ cpexec  ifconfig  mkfatfs   pwd   test
 usleep
  ? cmp   exit  ifdownmkrd  rmtime
 xd
  basename  dirname   false ifup  mount rmdir true
  break ddfree  kill  mvset   uname
  cat   dfhelp  lsnslookup  sleep umount

Builtin Apps:
  nimble  sh  nsh
nsh> nimble
nsh: nimble: command not found
nsh> ifconfig
bnep0   Link encap:UNSPEC at UP

nsh> nimble -h
nsh: nimble: command not found
nsh> nimble
nsh: nimble: command not found
nsh>

Initially I thought it was caused by recent update of the nimble stack
on NuttX, but I moved to a commit previous to that update and still
facing same error.

Matias, do you think it could be some issue with my crosscompiler?

I'm using the default ARM gcc from Ubuntu 20.04 gcc-arm-none-eabi package:

gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision
277599] (15:9-2019-q4-0ubuntu1)

Thank you very much!

BR,

Alan

On 5/25/21, Miguel Wisintainer  wrote:
> Matias
>
> Me and Alan will investigate!
>
> Thank you so much!
>
> Enviado do Email para
> Windows 10
>
>

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

Matias

Me and Alan will investigate!

Thank you so much!

Enviado do Email para Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Matias N.]

Hi Miguel,
from the looks of it, it is a problem with NuttX's Bluetooth host-layer. 
There's an unhandled opcode which corresponds to "scan enable", which is not 
being recognized when the controller sends "command complete".

In my case I used nimBLE for host layer which works well. You can try to 
reproduce nrf52832-mdk's sdc config which AFAIK is configured to use nimBLE.
I know others use other stacks but I'm not sure which one.

Best,
Matias

On Sun, May 23, 2021, at 19:01, Miguel Wisintainer wrote:
> 
> 
> 
> Hello Brennan
> 
> Plans changed, i had spent a lot of time today on NRF52832 then i suspect 
> that should be a Softdevice Version (132)
> Then i ported the NRF52840 and repeated all the process, and finally that 
> error was removed.
> Look the boot
> 
> ABCDEG
> bt_initialize: btdev 0x47384
> bt_hci_cmd_create: opcode 0c03 param_len 0
> bt_buf_alloc: buf 0x20002c40 type 0 reserve 0
> bt_hci_cmd_create: buf 0x20002c40
> bt_buf_extend: buf 0x20002c40 len 3
> bt_hci_cmd_send_sync: opcode 0c03 len 3
> hci_tx_kthread: started
> bt_buf_addref: buf 0x20002c40 (old) ref 1 type 0
> hci_tx_kthread: Sending command 0c03 buf 0x20002c40 to driver
> bt_hci_send: passing CMD 3075 to softdevice
> bt_buf_release: buf 0x20002c40 ref 2 type 0
> bt_buf_release: Remaining references: 1
> on_hci: received CMD_COMPLETE from softdevice (opcode: 3075, status: 0x3)
> bt_buf_alloc: buf 0x20002c28 type 1 reserve 1
> bt_buf_extend: buf 0x20002c28 len 6
> bt_hci_receive: buf 0x20002c28 len 6
> priority_rx_work: list 0x20002c64
> priority_rx_work: buf 0x20002c28 type 1 len 6
> bt_buf_consume: buf 0x20002c28 len 2
> hci_cmd_complete: opcode 0c03
> bt_buf_consume: buf 0x20002c28 len 3
> hci_reset_complete: status 0
> bt_buf_addref: buf 0x20002c28 (old) ref 1 type 1
> bt_buf_release: buf 0x20002c40 ref 1 type 0
> bt_buf_release: Buffer freed: 0x20002c40
> bt_buf_release: buf 0x20002c28 ref 2 type 1
> bt_buf_release: Remaining references: 1
> bt_buf_release: buf 0x20002c40 ref 0 type 0
> bt_buf_release: Remaining references: 255
> bt_buf_release: buf 0x20002c28 ref 1 type 1
> bt_buf_release: Buffer freed: 0x20002c28
> bt_hci_cmd_create: opcode 1003 param_len 0
> bt_buf_alloc: buf 0x20002c28 type 0 reserve 0
> bt_hci_cmd_create: buf 0x20002c28
> bt_buf_extend: buf 0x20002c28 len 3
> bt_hci_cmd_send_sync: opcode 1003 len 3
> bt_buf_addref: buf 0x20002c28 (old) ref 1 type 0
> hci_tx_kthread: Sending command 1003 buf 0x20002c28 to driver
> bt_hci_send: passing CMD 4099 to softdevice
> bt_buf_release: buf 0x20002c28 ref 2 type 0
> bt_buf_release: Remaining references: 1
> on_hci: received CMD_COMPLETE from softdevice (opcode: 4099, status: 0x3)
> bt_buf_alloc: buf 0x20002c40 type 1 reserve 1
> bt_buf_extend: buf 0x20002c40 len 14
> bt_hci_receive: buf 0x20002c40 len 14
> priority_rx_work: list 0x20002c64
> priority_rx_work: buf 0x20002c40 type 1 len 14
> bt_buf_consume: buf 0x20002c40 len 2
> hci_cmd_complete: opcode 1003
> bt_buf_consume: buf 0x20002c40 len 3
> hci_cmd_complete: Unhandled opcode 1003
> bt_buf_addref: buf 0x20002c40 (old) ref 1 type 1
> bt_buf_release: buf 0x20002c28 ref 1 type 0
> bt_buf_release: Buffer freed: 0x20002c28
> bt_buf_release: buf 0x20002c40 ref 2 type 1
> bt_buf_release: Remaining references: 1
> bt_buf_release: buf 0x20002c28 ref 0 type 0
> bt_buf_release: Remaining references: 255
> read_local_features_complete: status 0
> bt_buf_release: buf 0x20002c40 ref 1 type 1
> bt_buf_release: Buffer freed: 0x20002c40
> bt_hci_cmd_create: opcode 1001 param_len 0
> bt_buf_alloc: buf 0x20002c40 type 0 reserve 0
> bt_hci_cmd_create: buf 0x20002c40
> bt_buf_extend: buf 0x20002c40 len 3
> bt_hci_cmd_send_sync: opcode 1001 len 3
> bt_buf_addref: buf 0x20002c40 (old) ref 1 type 0
> hci_tx_kthread: Sending command 1001 buf 0x20002c40 to driver
> bt_hci_send: passing CMD 4097 to softdevice
> bt_buf_release: buf 0x20002c40 ref 2 type 0
> bt_buf_release: Remaining references: 1
> on_hci: received CMD_COMPLETE from softdevice (opcode: 4097, status: 0x1)
> bt_buf_alloc: buf 0x20002c28 type 1 reserve 1
> bt_buf_extend: buf 0x20002c28 len 14
> bt_hci_receive: buf 0x20002c28 len 14
> priority_rx_work: list 0x20002c64
> priority_rx_work: buf 0x20002c28 type 1 len 14
> bt_buf_consume: buf 0x20002c28 len 2
> hci_cmd_complete: opcode 1001
> bt_buf_consume: buf 0x20002c28 len 3
> hci_cmd_complete: Unhandled opcode 1001
> bt_buf_addref: buf 0x20002c28 (old) ref 1 type 1
> bt_buf_release: buf 0x20002c40 ref 1 type 0
> bt_buf_release: Buffer freed: 0x20002c40
> bt_buf_release: buf 0x20002c28 ref 2 type 1
> bt_buf_release: Remaining references: 1
> bt_buf_release: buf 0x20002c40 ref 0 type 0
> bt_buf_release: Remaining references: 255
> read_local_ver_complete: status 0
> bt_buf_release: buf 0x20002c28 ref 1 type 1
> bt_buf_release: Buffer freed: 0x20002c28
> bt_hci_cmd_create: opcode 1009 param_len 0
> bt_buf_alloc: buf 0x20002c28 type 0 reserve 0
> bt_hci_cmd_create: buf 0x20002c28
> bt_buf_extend: buf 0x20002c28 len 3
> 

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]

Sometimes show and disappears the nuttx on my ble scan

Enviado do Email para Windows 10

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Miguel Wisintainer]


Hello Brennan

Plans changed, i had spent a lot of time today on NRF52832 then i suspect that 
should be a Softdevice Version (132)
Then i ported the NRF52840 and repeated all the process, and finally that error 
was removed.
Look the boot

ABCDEG
bt_initialize: btdev 0x47384
bt_hci_cmd_create: opcode 0c03 param_len 0
bt_buf_alloc: buf 0x20002c40 type 0 reserve 0
bt_hci_cmd_create: buf 0x20002c40
bt_buf_extend: buf 0x20002c40 len 3
bt_hci_cmd_send_sync: opcode 0c03 len 3
hci_tx_kthread: started
bt_buf_addref: buf 0x20002c40 (old) ref 1 type 0
hci_tx_kthread: Sending command 0c03 buf 0x20002c40 to driver
bt_hci_send: passing CMD 3075 to softdevice
bt_buf_release: buf 0x20002c40 ref 2 type 0
bt_buf_release: Remaining references: 1
on_hci: received CMD_COMPLETE from softdevice (opcode: 3075, status: 0x3)
bt_buf_alloc: buf 0x20002c28 type 1 reserve 1
bt_buf_extend: buf 0x20002c28 len 6
bt_hci_receive: buf 0x20002c28 len 6
priority_rx_work: list 0x20002c64
priority_rx_work: buf 0x20002c28 type 1 len 6
bt_buf_consume: buf 0x20002c28 len 2
hci_cmd_complete: opcode 0c03
bt_buf_consume: buf 0x20002c28 len 3
hci_reset_complete: status 0
bt_buf_addref: buf 0x20002c28 (old) ref 1 type 1
bt_buf_release: buf 0x20002c40 ref 1 type 0
bt_buf_release: Buffer freed: 0x20002c40
bt_buf_release: buf 0x20002c28 ref 2 type 1
bt_buf_release: Remaining references: 1
bt_buf_release: buf 0x20002c40 ref 0 type 0
bt_buf_release: Remaining references: 255
bt_buf_release: buf 0x20002c28 ref 1 type 1
bt_buf_release: Buffer freed: 0x20002c28
bt_hci_cmd_create: opcode 1003 param_len 0
bt_buf_alloc: buf 0x20002c28 type 0 reserve 0
bt_hci_cmd_create: buf 0x20002c28
bt_buf_extend: buf 0x20002c28 len 3
bt_hci_cmd_send_sync: opcode 1003 len 3
bt_buf_addref: buf 0x20002c28 (old) ref 1 type 0
hci_tx_kthread: Sending command 1003 buf 0x20002c28 to driver
bt_hci_send: passing CMD 4099 to softdevice
bt_buf_release: buf 0x20002c28 ref 2 type 0
bt_buf_release: Remaining references: 1
on_hci: received CMD_COMPLETE from softdevice (opcode: 4099, status: 0x3)
bt_buf_alloc: buf 0x20002c40 type 1 reserve 1
bt_buf_extend: buf 0x20002c40 len 14
bt_hci_receive: buf 0x20002c40 len 14
priority_rx_work: list 0x20002c64
priority_rx_work: buf 0x20002c40 type 1 len 14
bt_buf_consume: buf 0x20002c40 len 2
hci_cmd_complete: opcode 1003
bt_buf_consume: buf 0x20002c40 len 3
hci_cmd_complete: Unhandled opcode 1003
bt_buf_addref: buf 0x20002c40 (old) ref 1 type 1
bt_buf_release: buf 0x20002c28 ref 1 type 0
bt_buf_release: Buffer freed: 0x20002c28
bt_buf_release: buf 0x20002c40 ref 2 type 1
bt_buf_release: Remaining references: 1
bt_buf_release: buf 0x20002c28 ref 0 type 0
bt_buf_release: Remaining references: 255
read_local_features_complete: status 0
bt_buf_release: buf 0x20002c40 ref 1 type 1
bt_buf_release: Buffer freed: 0x20002c40
bt_hci_cmd_create: opcode 1001 param_len 0
bt_buf_alloc: buf 0x20002c40 type 0 reserve 0
bt_hci_cmd_create: buf 0x20002c40
bt_buf_extend: buf 0x20002c40 len 3
bt_hci_cmd_send_sync: opcode 1001 len 3
bt_buf_addref: buf 0x20002c40 (old) ref 1 type 0
hci_tx_kthread: Sending command 1001 buf 0x20002c40 to driver
bt_hci_send: passing CMD 4097 to softdevice
bt_buf_release: buf 0x20002c40 ref 2 type 0
bt_buf_release: Remaining references: 1
on_hci: received CMD_COMPLETE from softdevice (opcode: 4097, status: 0x1)
bt_buf_alloc: buf 0x20002c28 type 1 reserve 1
bt_buf_extend: buf 0x20002c28 len 14
bt_hci_receive: buf 0x20002c28 len 14
priority_rx_work: list 0x20002c64
priority_rx_work: buf 0x20002c28 type 1 len 14
bt_buf_consume: buf 0x20002c28 len 2
hci_cmd_complete: opcode 1001
bt_buf_consume: buf 0x20002c28 len 3
hci_cmd_complete: Unhandled opcode 1001
bt_buf_addref: buf 0x20002c28 (old) ref 1 type 1
bt_buf_release: buf 0x20002c40 ref 1 type 0
bt_buf_release: Buffer freed: 0x20002c40
bt_buf_release: buf 0x20002c28 ref 2 type 1
bt_buf_release: Remaining references: 1
bt_buf_release: buf 0x20002c40 ref 0 type 0
bt_buf_release: Remaining references: 255
read_local_ver_complete: status 0
bt_buf_release: buf 0x20002c28 ref 1 type 1
bt_buf_release: Buffer freed: 0x20002c28
bt_hci_cmd_create: opcode 1009 param_len 0
bt_buf_alloc: buf 0x20002c28 type 0 reserve 0
bt_hci_cmd_create: buf 0x20002c28
bt_buf_extend: buf 0x20002c28 len 3
bt_hci_cmd_send_sync: opcode 1009 len 3
bt_buf_addref: buf 0x20002c28 (old) ref 1 type 0
hci_tx_kthread: Sending command 1009 buf 0x20002c28 to driver
bt_hci_send: passing CMD 4105 to softdevice
bt_buf_release: buf 0x20002c28 ref 2 type 0
bt_buf_release: Remaining references: 1
on_hci: received CMD_COMPLETE from softdevice (opcode: 4105, status: 0x9)
bt_buf_alloc: buf 0x20002c40 type 1 reserve 1
bt_buf_extend: buf 0x20002c40 len 12
bt_hci_receive: buf 0x20002c40 len 12
priority_rx_work: list 0x20002c64
priority_rx_work: buf 0x20002c40 type 1 len 12
bt_buf_consume: buf 0x20002c40 len 2
hci_cmd_complete: opcode 1009
bt_buf_consume: buf 0x20002c40 len 3
hci_cmd_complete: Unhandled opcode 1009
bt_buf_addref: buf 0x20002c40 (old) 

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Brennan Ashton]

On Sun, May 23, 2021, 6:32 AM Miguel Wisintainer 
wrote:

> Sir
>
> How are you ?
>
> I compiled the SDC Nimble to run on NRF52832 but i am getting the
> following error
>
> NuttShell (NSH) NuttX-10.1.0-RC1
> nsh> ERROR: nrf52_sdc_initialize() failed: -45
>

You will likely need to turn on the wireless debug error logging to see the
failure here, otherwise it will be hard to know which part of the
initialization failed.

https://github.com/apache/incubator-nuttx/blob/c55085c0d8864c9401de97872ab3463d474f262c/arch/arm/src/nrf52/nrf52_sdc.c#L403

--Brennan

Re: Nimble on U-blox Nina B112 (Nrf52832)

[Alan Carvalho de Assis]

Hi Miguel,

We didn't receive your config, please rename it to config.txt and send
again.

BR,

Alan

On Sunday, May 23, 2021, Miguel Wisintainer  wrote:

> Sir
>
> How are you ?
>
> I compiled the SDC Nimble to run on NRF52832 but i am getting the
> following error
>
> NuttShell (NSH) NuttX-10.1.0-RC1
> nsh> ERROR: nrf52_sdc_initialize() failed: -45
>
> Can you help me ?
>
> Thanks
>
> Attached the config
>
> Miguel Wisintainer
>