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
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]
B
Suzuki-san,
Please send a PR (Pull Request) to
https://github.com/apache/incubator-nuttx-apps/
On Thu, Dec 10, 2020 at 5:24 PM SUZUKI Keiji wrote:
> Hi,
>
> I use STM32F407G-DISC1 (MB997D) and build nuttx on macOS Mojave (10.14.6).
>
> The following error occurs with the default configuration o
Hi Xiang,
thanks for your reply and for your work on armv8-m.
Bye,
Michael
Am Do., 10. Dez. 2020 um 15:40 Uhr schrieb Xiang Xiao <
xiaoxiang781...@gmail.com>:
> On Wed, Dec 9, 2020 at 10:48 PM Michael Jung wrote:
>
> > Hello,
> >
> > I recently bought an STM32L52E-DK development kit and I am
On Wed, Dec 9, 2020 at 10:48 PM Michael Jung wrote:
> Hello,
>
> I recently bought an STM32L52E-DK development kit and I am playing around
> with ST's port of ARM's TrustedFirmware-M (see ST's UM2671). I would like
> to basically leave this untouched, but replace ST's 'non-secure'
> demo-applica
I think the issue is that you need to halt execution right before all registers
are touched in the handler.
The problem I always found is that at this point it doesn't mean execution
arrived there due to a hardfault
as this is also used for context switches (so placing a breakpoint there is o
I always wondered if we could improve the hardfault debugging experience
somehow. One option
is to extend the gdbinit script to do this as a command. I'm not sure if it is
a failproof procedure though,
as the LR sometimes simply contained the address of other instructions inside
the hardfault ha
Hi everybody!
I am trying to use the ADC on an STM32F427.
I am able to properly register the driver and access the ADC device.
However, I am really confused on the proper use of the driver.
I have 8 ADC-capable pins on my board that I want to read.
I want to achieve the following sequence:
1. Se
Hi Brennen,
I have not tested with vscode in a bit. But the issue for me before was the
edit ability of registers on IP blocks and CPU. Ben may be referring to the
hard fault debugging technique I presented at the NuttX conference 2 years
ago. It is a simple cut and paste from the LR to the IP reg
Try my blog http://nuttx.nl (english) or I can help you set it up.
Hope this will get you going!
Op do 10 dec. 2020 2:30 a.m. schreef Marlar Chan :
> Dear Ben,
>Is there any setup guideline for Nuttx debuggig with VSCode (normal
> use) and Eclipse (Hard faults)?
>
> Best Regards,
> Marlar
>
A mixture my c_cpp_properties.json looks like this:
{
"configurations": [
{
"name": "Linux",
"defines": [],
"includePath": ["${workspaceRoot}/**"],
"compilerPath":
"/home/bashton/toolchains/gcc-arm-none-eabi-8-2019-q3-update/bin/arm-none-eabi-gcc",
"compileCommands": "${workspaceRoot}/nuttx/compile
Suzuki,
There were a handful of changes in the 10.0.0 release related to this
that are discussed here:
https://github.com/apache/incubator-nuttx/issues/2203
If you could comment there it might be easier to get the attention of
the people involved in the change.
I had not followed it as closely so
Hi,
I use STM32F407G-DISC1 (MB997D) and build nuttx on macOS Mojave (10.14.6).
The following error occurs with the default configuration of
stm32f4discovery:usbnsh.
NuttShell (NSH) NuttX-10.0.0
nsh> nsh: nsh_session: readline failed: 9
The reason seems that instream->fs_fd is -1 instead of
13 matches
Mail list logo
