On Sun, Jan 12, 2020 at 2:20 AM Gregory Nutt wrote:
>
>
> > I fixed this section of code because it had ETIMEOUT instead of
> > ETIMEDOUT and so caused a compilation failure.
> >
> > Looking more carefully, net_timedwait() will return -ETIMEDOUT on the
> > timeout. So shouldn't the condition be (
Why is the CS not pulled low at the end? So it can receive the last 0xFF?
When I bypass the gate it is working.. Using the gate it is not?
Thanks
Ben
Hi Ben,
You need to describer better your issue and what you are trying to do.
We cannot guess what is happening at your side.
Normally the /CS should goes low before the SPI data transfer and
should go high at end of the transfer. So if you are connecting it to
74AHC1G125 to /OE you should see t
Hi Ben,
I saw the circuit you sent privately to me. Actually you are using the
74AHC1G125 as buffer to MISO signal, not MOSI as I was thinking.
I see no reason it is not working, did you try to change the SPI frequency?
BR,
Alan
On 1/12/20, Alan Carvalho de Assis wrote:
> Hi Ben,
>
> You need
It was a bug in thttpd – it wasn't accounting for the length of the headers
properly. I'll make a PR for it once I get a few other issues worked out.
The thttpd performance is a lot worse then uIP webserver– this shouldn't be
the case. Maybe there is a resource bottleneck of some kind. I tried
Yes I did. It seems that every SPI board already has this functionality... its
working when I bypass the gate.
Verstuurd vanaf mijn iPhone
> Op 12 jan. 2020 om 15:25 heeft Alan Carvalho de Assis het
> volgende geschreven:
>
> Hi Ben,
>
> I saw the circuit you sent privately to me. Actually
> The first thing I would do would be to use Wireshark to see what exactly
> the timing on the network is.
>
Greg,
Thanks- that sounds good. Would you be willing to say more about this? What
exactly would you look for?
I also plan to hook up a gigabit Ethernet from the board to my laptop to
see
The first thing I would do would be to use Wireshark to see what exactly
the timing on the network is.
Greg,
Thanks- that sounds good. Would you be willing to say more about this? What
exactly would you look for?
You should see the connection, the HTTP requests and the HTTP responses,
and
Greg,
Ok, thanks. I did do that yesterday with tcpdump while trying to find the
closing-early problem with the header lengths. Now with the header length
calculation things look good– at low speeds, the packet exchange matches
what I am getting from a Linux web server. No retransmissions, resets,
Ok, thanks. I did do that yesterday with tcpdump while trying to find the
closing-early problem with the header lengths. Now with the header length
calculation things look good– at low speeds, the packet exchange matches
what I am getting from a Linux web server. No retransmissions, resets, or
On Sun, Jan 12, 2020 at 1:27 PM Disruptive Solutions
wrote:
>
> Yes I did. It seems that every SPI board already has this functionality...
> its working when I bypass the gate.
>
> Verstuurd vanaf mijn iPhone
>
> > Op 12 jan. 2020 om 15:25 heeft Alan Carvalho de Assis
> > het volgende geschreve
Thanks, that document is very helpful. I set up TCP Blaster as a client,
not a server, just because it was easier for me to send data from Linux
with netcat. I'll try it as a server, I just have to look up the right
netcat params.
I am glad to hear from you that's your experience was that NuttX is
Thanks, that document is very helpful. I set up TCP Blaster as a client,
not a server, just because it was easier for me to send data from Linux
with netcat. I'll try it as a server, I just have to look up the right
netcat params.
I am not sure if you should not use netcat. When you build
a
Greg,
Thanks, I will try to use the host client programs. I just need to see if I
can get them compiled on Linux.
Re: link speed, 100 Mbps using Ethernet over USB would work. Higher would
be better. The network I want this to work on is just from the NuttX box to
the host computer. The host is di
I have a SAMA5D36-Xplained. I have configured NuttX to use the GMAC gigabit
ethernet as eth0, and EMACA 10/100 ethernet as eth1.
NuttX compiles and runs. When I do ifconfig, I see both interfaces. But I
plug an ethernet cable into either port and into my laptop's ethernet port,
neither interface w
NuttX compiles and runs. When I do ifconfig, I see both interfaces. But I
plug an ethernet cable into either port and into my laptop's ethernet port,
neither interface will come up:
nsh> ifconfig
eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 at DOWN
inet addr:107.127.109.40 DRaddr:107.127
On Tue, Jan 7, 2020 at 5:09 PM Gregory Nutt wrote:
>
> The removal of (void) from all functions whose return value has been
> ignored has introduced several new warnings into the build test output.
> For example in lpc3_appinit(), I now see this:
>
> # define nsh_spifi_initialize() (OK)
>
> a
So I guess our choices are:
1. Reinstate (void) only where the warning occurs.
2. Reinstate (void) everywhere return values aren't checked. What a nightmare.
3. Change defines such as the above to static inline functions.
Disadvantage: The inline keyword is not in the C89 standard.
I have
So I guess our choices are:
1. Reinstate (void) only where the warning occurs.
2. Reinstate (void) everywhere return values aren't checked. What a
nightmare.
3. Change defines such as the above to static inline functions.
Disadvantage: The inline keyword is not in the C89 standard.
I h
I have ran the build tests and do not know of any other cases like
this. ...
That needs clarification. I have been starting the build tests everyday
for the past weeks, but there has been no successful, complete run of
the ARM builds in the past 3 weeks. The build has been broken every d
On Sun, Jan 12, 2020 at 3:08 PM Gregory Nutt wrote:
> Have you turned on network debug output? At least errors and warnings.
>
Yes, I have the following set:
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_NET_INFO=y
> eth1 has no MAC address.
>
H. How do I set this? Where is eth0's MAC set?
> Are y
What needs to be done to move closer to release?
On other projects I've been on, we froze the master branch except for
bugfix commits (did not merge new features), and iterated until things
stabilized. Can we do that here?
As to having a release manager, what's involved in that? Is there a role
d
eth1 has no MAC address.
H. How do I set this? Where is eth0's MAC set?
eth0 will be configured by apps/netutils/netinit. Bit it will
initialize only one network. It will require custom logic to initialize
two networks.
Have you tried: nsh>ifup eth0
No. Bravo! That got the interfac
I fixed the routing table on my laptop and can ping the Nuttx board now;
and the NuttX board can ping the laptop. Super!
NuttX reports an ethernet address of ff:ff:ff:ff:ff:ff though. I'll look
into how to add logic to set a better ethernet address.
I'll do some bandwidth tests tomorrow with the
NuttX reports an ethernet address of ff:ff:ff:ff:ff:ff though. I'll look
into how to add logic to set a better ethernet address.
Not a problem. That is the broadcast address
The GMAC at eth0 also works! :)
On Sun, Jan 12, 2020 at 6:57 PM Gregory Nutt wrote:
> > NuttX reports an ethernet address of ff:ff:ff:ff:ff:ff though. I'll look
> > into how to add logic to set a better ethernet address.
> Not a problem. That is the broadcast address
>
--
Adam Feuer
The GMAC at eth0 also works! :)
There is a good dual network test at apps/examples/bridge. There is a
description in the Kconfig there. There are test configurations here:
boards/arm/sama5/sama5d3-xplained/configs/bridge
boards/arm/sama5/sama5d4-ek/configs/bridge
That should, at lease, show
27 matches
Mail list logo
