gpio interrupts for lpc43xx


I have a board with the lpc4337 chip and I'm trying to get interrupts for a given pin for developing a ping-echo sonar driver. I'm having problems receiving the interrupt, it does not seem to be generated. I have a pin set as output acting as a trigger (it sends a 10us pulse) connected to what would be the echo receive pin (for test purposes), which is configured as pin interrupt. 

This is the relevant code: https://gist.github.com/v01d/81795f124f280fa48e885fabab1fcf04

The driver calls initialize() and sets the pins. Then upon a read() call it calls enable() (which sets up t he interrupt and handler) and then calls the trigger(). I can see the pulse on a scope and it would seem that the pin configurations are correct. I tried by different means to check if the interrupt is received and it would not seem so (I even set the handler point to a random value to trigger a crash).

Am I missing something?

Btw, I had to define CONFIG_GPIO_IRQ for my board to get the relevant functionality to compile. 

Thank you!


Posted by: phreakuencies-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org


ms58xx for ms583730


A patch to:

* fix a bug in crc computation for ms583730

* implement POSIX read.



Posted by: pn_bouteville-Qt13gs6zZMY@public.gmane.org


Multiple PWM channel on Timer 4 for STM32F4Discovery


I've been looking into PWM driver and example lately and understood that only channel 2 from timer 4 is associated with the PWM example, which i ran and tested successfully.
The thing is i would like to open up a second PWM channel ( channel 3 from timer 4 preferably), is that possible? Since there is a PWM multi-channel support option.
And there is also the option of creating a second pwm device from the other timers.

Thank you for reading.

Posted by: lad.allena-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


alternative to usingt kfifo*


I am trying to port a driver from linux to nuttx. It uses a lot of the kfifo_* functions and char device functionality. Can anyone recommend a good alternative to use on nuttx? 

(i am using flat mode if that changes anything)

Posted by: kim-ppvRghqR8ddaa/9Udqfwiw@public.gmane.org


ADC without "upper half" driver


I need to use only lowlevel adc driver (stm32_adc) in an motor driver.

I just need to catch adc_receive function.

What the best way to do it ?


Posted by: pn_bouteville-Qt13gs6zZMY@public.gmane.org


Test suit for Net stack components

Dear Greg,

I wanted to know how we can maintain the quality parameter for Net stacks ?

As i learn, For IPv6, there is TAHI test suit (http://www.tahi.org/conformance/) which will give us the quality of IPv6 stack( It has around 380 test cases to cover almost everything). 

But for the other modules such as TCP, IPv4, UDP etc I am unable to find any test suit which will verify the functionality.

Can you please let us know if you know how we can maintain the quality attributes of TCP, UDP, IPv4 ?

If we have any tool which will take care of it, We are always sure that quality/functionality of the Net stack is not broken with some latest changes. p>

Please guide us here.

Thanks in advance,


Posted by: rajuuu1992-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


PATCH: LPC4337JET100 chip definition [1 Attachment]

Please, add definition for LPC4337jet100 chip.


Attachment(s) from alexander.vasiljev-/E1597aS9LQAvxtiuMwx3w@public.gmane.org [nuttx] | View attachments on the web

1 of 1 File(s)

Posted by: alexander.vasiljev-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


PATCH: AES on LPC43Sxx [2 Attachments]

LPC43Sxx chips have hardware AES support. Here are patches to support aes functionality. However, it had to change current crypto api.


Attachment(s) from alexander.vasiljev-/E1597aS9LQAvxtiuMwx3w@public.gmane.org [nuttx] | View attachments on the web

2 of 2 File(s)

Posted by: alexander.vasiljev-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


how to register drivers outside board specific logic

I'm currently using an arduino-like board as part of a larger project, connected to external devices (such as i2c devices). This board is not currently supported by NuttX so I'm also adding support for it in "configs/". However, I would like to not tie the registration of devices which I'm using with this board, to the support code for this board itself, which should be generic if used in other projects. 

I would like to know if it is possible to register devices outside of this logic, maybe in my own application (which is specific to the board being used with other devices) or, even better, as part as a custom boot script which creates devices files associated to a specific driver.



Posted by: phreakuencies-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org


PATCH: Enhance simulation networking in Linux [1 Attachment]

Hiya, folks.

I've been playing with NuttX for about a week now, and so far I'm pretty happy
with it.  I did find an issue with the simluation's network code, however, so
I set about making it work for my environment (which turned into more
extensive work than I intended, but oh well).  Please find information on the
attached patch below.  Greg, please feel free to merge if you like it.

- Steve

   This patch enhances networking support for the simulation under Linux.
   Includes updated support for Linux TUN/TAP, and the addition of support for
   Linux bridge devices.

   o Check to see if the d_txavail callback is present before calling it in
     the arp send code.  This prevents a segfault when simulating the telnetd
     daemon with arp send enabled.

   o Adjust the simulation's netdriver_loop() so it will detect and respond to
     ARP requests.

   o Do not attempt to take the tap device's hardware address for use by the
     simulation.  That hardware address belongs to the host end of the link,
     not the simulation end.  Generate a randomized MAC address instead.

   o Do not assign an IP address to the interface on the host side of the TAP

   + Provide two modes: "host route" and "bridge".

   + In host route mode, maintain a host route that points any traffic for the
     simulation's IP address to the tap device.  In this mode, so long as the
     simulation's IP is a free address in the same subnet as the host, no
     additional configuration will be required to talk to it from the host.
     Note that address changes are handled automatically if they follow the
     rule of if-down/set-address/if-up, which everything seems to.

   + In bridge mode, add the tap device to the specified bridge instance.  See
     configs/sim/NETWORK-LINUX.txt for information and usage examples.  This
     enables much more flexible configurations (with fewer headaches), such as
     running multiple simulations on a single host, all of which can access
     the network the host is connected to.

   o Refresh configurations in configs/sim where CONFIG_NET=y.  They default
     to "host route" mode.

   o Add configs/sim/NETWORK-LINUX.txt

   - The MAC address generation code is extremely simplistic, and does not
     check for potential conflicts on the network.  Probably not an issue, but
     something to be aware of.

   - I was careful to leave it in a state where Cygwin/pcap should still work,
     but I don't have a Windows environment to test in.  This should be

   - I don't know if this was ever intended to work with OS X.  I didn't even
     try to test it there.

   - Was able to get telnetd working and simulate nsh over telnet, but only so
     long as listen backlogs were disabled.

     There appears to be a bug in the backlog code where sockets are being
     returned in SYN_RCVD state instead of waiting until they're ESTABLISHED;
     if you perform an immediate send after accepting the connection, it will
     confuse the stack and the send will hang; additionally, the connection
     will never reach ESTABLISHED state.

     Can be worked around by adding a sleep(1) after the accept in telnetd.  I
     don't have the necessary knowledge of the IP stack to know what the
     correct fix is.

   - If you would prefer this in the form of a merge request, let me know.

Attachment (nuttx-sim-network.patch.gz): application/x-gzip, 11 KiB


[PATCH] stm32f103-minimum: Add instructions to use 128KB instead of 64KB [1 Attachment]

<*>[Attachment(s) from Alan Carvalho de Assis included below]

Hi Greg,

Please find attached a patch to include the instructions to write
NuttX to 128KB on STM32F103C8.



<*>Attachment(s) from Alan Carvalho de Assis:

<*> 1 of 1 File(s)
  <*> 0001-stm32f103-minimum-Add-instructions-to-use-128KB-inst.patch

Posted by: Alan Carvalho de Assis <acassis@...>


Yahoo Groups Links

<*> To visit your group on the web, go to:

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    (Yahoo! ID required)

<*> To change settings via email:

<*> To unsubscribe from this group, send an email to:

<*> Your use of Yahoo Groups is subject to: