ADXL372_test (SPI Configuration issue)

2020-12-03 Thread Marlar Chan
Dear Nuttx,

  Currently I am testing with STM32F429_waveshare. It is same with 
STM32F429_disco, so I add the new board into Nuttx.
Now, I'm trying to test with adxl372 sensor with the board. I use SPI so in 
menu config, I enable SPI driver and sensor driver. But in nsh, it cannot show 
the usb dev. I use with the command: ls /dev. I also tried enable 
stm32_adxl345. For adxl372, I'm not clear STM32F429_disco use SPI 5 or SPI1. I 
found it use SPI5 for MEMS in the code. However, even I tried with both,  both, 
it cannot show sensor device in nsh. Can you suggest me anything!


Thank you,
Best Regards,
Marlar



CONFIDENTIALITY: This email is intended solely for the person(s) named and may 
be confidential and/or privileged. If you are not the intended recipient, 
please delete it, notify us and do not copy, use, or disclose its contents.
Towards a sustainable earth: Print only when necessary. Thank you.


Re: about IDEs and dev boards

2020-12-09 Thread Marlar Chan
Dear Ben,
   Is there any setup guideline for Nuttx debuggig with VSCode (normal use) and 
Eclipse (Hard faults)?

Best Regards,
Marlar

From: Disruptive Solutions 
Sent: Wednesday, December 9, 2020 6:16 PM
To: dev@nuttx.apache.org 
Subject: Re: about IDEs and dev boards

VSCode (normal use) and Eclipse (Hard faults).

STM32 stack (nucleos, blackboards, etc) and own reference board(s).

Hardware as extra tools (logic analyzer, scope, seggers, st link, etc)

And just having fun to use NuttX and the results one can achieve. Still
mind blowing!!!

Ben

Op wo 9 dec. 2020 8:39 a.m. schreef Marc Rosen :

>
> Am 04.12.2020 um 02:54 schrieb Matias N.:
> > Hi,
> > I was wondering what IDEs do you use with NuttX and what is your
> preferred dev board (can be more than one).
> > I'm curious since I have used QtCreator for long time now and generally
> works well, but it has some quirks.
> Jetbrains CLion is the IDE i use. It is not that great with Makefile
> projects and debugging but it is getting better.
> And it works well if you also use some of their other dev tools and ides.
> > And on hardware side I always favored STM32 boards (with embedded
> debugger) but after getting into nRF52 I found
> > it to be much easier to work with and seems a very well designed SoC
> from the users perspective. The "mux (almost) any peripheral to any pin" is
> great (any other chip does that?).
> >
> > Best,
> > Matias
> Mostly AVRs here, the ones too small for Nuttx, and STM32. Usually
> custom boards.
>
> regards,
> Marc
>
>


CONFIDENTIALITY: This email is intended solely for the person(s) named and may 
be confidential and/or privileged. If you are not the intended recipient, 
please delete it, notify us and do not copy, use, or disclose its contents.
Towards a sustainable earth: Print only when necessary. Thank you.


ADXL372 sensor test fail

2020-12-10 Thread Marlar Chan
Dear Nuttx,
   I'm testing with stm32f429-disco with adxl372 sensor. I tried to run sample 
demo adxl372_test. Device id is seen on /dev. But sensor cannot start run and i 
face with the following issue. Please suggest me any idea what is wrong with it.
[cid:8a35bb4c-af2d-4429-bf1a-ba83816d1ac9]

Best Regards,
Marlar


CONFIDENTIALITY: This email is intended solely for the person(s) named and may 
be confidential and/or privileged. If you are not the intended recipient, 
please delete it, notify us and do not copy, use, or disclose its contents.
Towards a sustainable earth: Print only when necessary. Thank you.


Re: ADXL372 sensor test fail

2020-12-17 Thread Marlar Chan
Dear Nuttx,


I'm trying according to your instructions. But still cannot read sensor. I 
don't understand why ID is 0x.
[cid:07735f7d-1a47-42b7-b827-0e7af231fa04]
Is it related with SPI CS pin. I tried with MEMS Chip select pin to

  1.   ground

 2.  PC1
[cid:9cafed8e-3666-4626-8067-702173b5350c]3. PF6(NSS pin)

But still I cannot get data from sensor. Can you suggest me please.

And according to your instuction,
$ make menuconfig

Build Setup  --->
Debug Options  --->

[*] Enable Debug Features
[*]   Enable Error Output
[*] Enable Warnings Output
[*]   Enable Informational Debug Output

[*]   Sensor Debug Features
[*] Sensor Error Output
[*] Sensor Warnings Output
[*] Sensor Informational Output

I enable these in menu config, how can i check sensor error ouput, warning 
output, etc. Please advise me.


Best Regards,
Marlar

From: Alan Carvalho de Assis 
Sent: Friday, December 11, 2020 7:07 PM
To: dev@nuttx.apache.org 
Cc: Shee Cheng Yap 
Subject: Re: ADXL372 sensor test fail

You need to enable the Sensors debug to see these sensor's messages:

$ make menuconfig

Build Setup  --->
Debug Options  --->

[*] Enable Debug Features
[*]   Enable Error Output
[*] Enable Warnings Output
[*]   Enable Informational Debug Output

[*]   Sensor Debug Features
[*] Sensor Error Output
[*] Sensor Warnings Output
[*] Sensor Informational Output

BR,

Alan

On 12/11/20, Xiang Xiao  wrote:
> nuttx/include/errno.h define ENODEV to 19:
> #define ENODEV  19
> and nuttx/drivers/sensors/adxl372.c return ENODEV  if id mismatch:
> static int adxl372_dvr_open(FAR void *instance_handle, int32_t arg)
> {
>   /* Read the ID registers */
>
>   pnpid = adxl372_read_id(priv);
>   priv->readonly = false;
>
>   sninfo("ADXL372_ID = 0x%08x\n", pnpid);
>
>   if ((pnpid & 0xff00) != (ADXL372_DEVID_AD_VALUE << 24 |
>ADXL372_DEVID_MST_VALUE << 16 |
>ADXL372_PARTID_VALUE << 8))
> {
>   snwarn("ERROR: Invalid ADXL372_ID = 0x%08x\n", pnpid);
>
>   priv->readonly = true;
>   set_errno(ENODEV);
> }
> You have to check what's the value in pnpid.
>
> On Fri, Dec 11, 2020 at 2:28 PM Marlar Chan  wrote:
>
>> Dear Nuttx,
>>I'm testing with stm32f429-disco with adxl372 sensor. I tried to run
>> sample demo adxl372_test. Device id is seen on /dev. But sensor cannot
>> start run and i face with the following issue. Please suggest me any idea
>> what is wrong with it.
>>
>> Best Regards,
>> Marlar
>> --
>>
>> CONFIDENTIALITY: This email is intended solely for the person(s) named
>> and
>> may be confidential and/or privileged. If you are not the intended
>> recipient, please delete it, notify us and do not copy, use, or disclose
>> its contents.
>> Towards a sustainable earth: Print only when necessary. Thank you.
>>
>