willmore

For me "time is the missing ingredient" ...
If you have some spare time, you could check the latency time between the FIFO fills, and also if CS is asserted during the whole large transfer, not only during the FIFO size of 64 bits.

I doubt there will be huge performance gain, because even with DMA, there will be some latency for DMA buffer been filled.
When I ported the FIFO large transfer, I said that when I get a chance, I will check the latency with logic analyser, but I didn't got chance yet.

He means mainline u-boot SPI driver - to be able to store environment and use MTD partitions from u-boot proper.

It is good to disable it in the DT, but I presume leaving PA20 floating won't disable power since floating has similar effect to HIGH level on most chips.

Do you want to know the dimensions to create box for 3D printers?
 
If yes, there is already something in thingiverse I've already printed, working fine :
1 - http://www.thingiverse.com/thing:1986658
2 - http://www.thingiverse.com/thing:1918590
 
You can get the files and open them with freecad for example, so there you can grab the measurements. 

Make sure that PA20 is LOW, it is the WIFI-POWER-EN.

For the 78xx electrolytic cap should be on input and ceramic cap should be on output (as close to the regulator as possible). For all types of regulators looking at the datasheet is recommended before trying to apply a common sense - some require a ceramic cap on the output while others require electrolytic one for the stability.
In any case 78xx or any kind of linear regulator should not be used here - it will consume more power than the board itself at this voltage difference.

The PSU looks ok but it would be great when you run a 'stress -c 2 -m 2' on the board and then measure voltage available at the Expansion board (pins) just to ensure you're not running in undervoltage trouble. I tested with Orange Pi PC a year ago and this one worked flawlessly with just 4.5V input voltage (though neither USB nor HDMI connected -- both ports require a lot more than 4.5V as minimal voltage) but no idea about the Zero.
 
If I remember correctly almost all reports related with network negotiation problems (the half duplex issue) are reports from those H3 boards using shitty Micro USB for DC-IN. So I thought it might be worth a look whether we're not talking about power problems instead (also IIRC the Fast Ethernet PHY inside H2+/H3 needs 1.2V provided by some regulator and in case this regulator is not linear a drop in input voltage might affect networking negotiation).
 
BTW: Am currently also in France. We bought yesterday a rather expensive 5V/2A rated PSU at Carrefour and drive now back to return it. Death on arrival or let's better say the usual 'undervoltage under load' problem

Will be done eventually. We already have a pretty big DT patch for this board.
 
Last time I edited the kernel config I enabled almost all Realtek wireless drivers that were available.

Nope, and usually when I add Xunlong stuff to the wiki it was Igor who got it since he communicates way more frequently with vendors than I do.
 
@Igor: Chinese New Year is over now. Could you please ask Steven to provide schematic for the NAS board?

Well, on the first pages of the mainly mis-used 'Orange Pi Zero went to the market' thread there were some idle consumption numbers and everything else depends on usage. See difference between idle and 'full load' numbers for H3 here (and keep in mind that Zero default settings are for IoT and therefore low consumption) and add consumption of connected peripherals.
 
My understanding is that powering the NAS Expansion board through the 4/1.7mm barrel plug should provide 3.3V/5V to a connected mSATA disk, 5V to the SATA power port and also the Zero where this voltage is also available at the power pins of the Type A receptacle (without the usual 500mA restriction of USB2 ports on 'real computers' but providing more -- still too lazy to check schematics whether there is some sort of current control or not). Using Xunlong's 5V/3A PSU should suffice to power board, a mSATA SSD and 2 2.5" disks (one connected to SATA + SATA power port, the other via USB).
 
BTW: 3.5" disks with own PSU need just a small/cheap mechanical converter if the SATA port is already used:
 

 
 
There's a SATA power connector on the board and adapter cables exist, eg. https://www.aliexpress.com/item/SATA-Line-for-orange-Pi-Free-shipping/32248261533.html
 
Please be aware that 4 vendors sell these cables but polarity of the 5V lines differs! See https://forum.armbian.com/index.php/topic/3387-nas-on-banana-pi-need-advice-on-power-supply/?p=24467 for details.
 
Edit: Since Xunlong designed the original Banana Pi and used the same SATA connector on the first A20 based Orange Pi i would assume polarity of the SATA power connector to be compatible to the SATA cable kit they sell. But this needs to be confirmed!

Okay, I took a multimeter to my NAS board.  There isn't conductivity between the host side power and the jack on the board.  There are two diodes in parallel that isolate the NAS board jack from the 5V the host provides.  The diodes are in the direction that the jack *could* supply power back to the host.  The two diodes are Schottky devices, so the voltage drop through them should be fairly low for the currents the Z can pull.  That might be different for an H5 based host.
 
@tkaiser, you probably have better data on that.  My general observation is that the Z uses around half the current of the PC2.
 
I'm going to try powering things on soon.

I printed a case for my PC2 today and reran the thermal soak using cpuminer.  Old score (stock board, mainline kernel, no enhanced airflow) was around 3.2KH/s.  Now, in the case it's running 2.6KH/s and is around 5 degrees cooler.
 
So, it looks like the DVFS/thermal budget cooling code works pretty well.  Shall I tape up the box so there's no airflow?

You're welcome to submit a u-boot patch to support it faster.

Ah, now I got your point. Since we (the community) are 'competing' with commercial entitites and we do our work for free it can't have any value or be as good as 'paid contribution'. Now I understand why you're thinking the stuff community does is worse compared to paid jobs (you're good in blindly adopting marketing BS even if you seem to have no clue about the nature of Open Source development)
 
 
Yes, and by letting your f*cking market trashtalking all the time this thread has now 10 pages with all real information got lost somewhere on the first pages. I would love to see the market shutting up now forever (at least here in Armbian forum!)
 
 
 
You called NAND eMMC which is plain wrong. Could you please stop flooding this forum with misleading assumptions and all this useless and stupid valuations?!
 
No one so far correctly benchmarked OPi Zero WiFi, we got only a lot of confusing feedback and still have no clue what the issues with this WiFi chip or the various drivers are. Doing such a benchmark correctly is not that easy and time consuming and as Zador already said it's stupid anyway to even try to benchmark this el cheapo WiFi crap (this applies to all these single antenna, non-MIMO, 2.4 GHz only crap chips on all the cheap SBC around)

OpenWrt is far more suited to industrial environments. Most OpenWrt hardware uses NOR flash, which does not degrade via reads, NAND does.
 
Wikipedia has more details on this: https://en.wikipedia.org/wiki/Flash_memory#Read_disturb
 
You can even buy OpenWrt devices which use NAND, if you need more storage. These routers have more than enough horse power for almost any M2M application, and you can buy them pretty cheap: https://www.aliexpress.com/item/Original-Xiaomi-WIFI-Router-3-WiFi-Repeater-1167Mbps-2-4G-5GHz-ROM-128MB-Wi-Fi-Roteador/32688259842.html
 
 
 
Supporting Linux on these cheap SBCs is not a total waste of time, but it might be for your use case.
 
Yes, you absolutely need to buy multiple boards and test them for your use case. Or you can call a distributor like Digikey and ask them for the right board for your application. You will pay a lot more for this, it won't be as new as the Orange Pi Zero, it will probably use some vendor proprietary toolchain and Linux image, but it will work for 10 years and your customers won't hate your product because you thought it would be good to build it around a $10 SBC from China.
 
 
No one is saying you can expect stability from an Orange Pi Zero for your use case. You need to test it yourself and figure out whether it's stable or not. We don't have the resources to test the hardware in your use case.
 
Please, email Xunlong and ask your questions. See if you get any response back, or how helpful it is.
 
This forum has a search feature. A contributing factor to this "abusive language" as you put it, is that 20 people ask the same questions over and over again instead of searching the forum for the last time this question was asked, looking at the answer, and then accepting that the situation isn't as they had hoped.

Show me where on that page is says "AP"
 
A wireless server can be any computer connected via WiFi which exchanges data. e.g. it's connected as a client and runs an HTTP server where you can download files.
 
Boom! Wireless. Server.
 
 
 
So you won't donate to us, volunteers who spend our own time and money to buy the hardware and improve it, because we didn't make a perfect product that can do everything you dream of?
 
 
If people like you didn't complain so much, we might actually have the time and motivation to do "innovation"
 
This is the n'th time you've suggested that we take even more time away from "innovation" to create an FAQ for lazy people like you who can't be bothered to read the forum or mailing list.
 
I will again suggest that you can spend your own time making the monthly FAQ, instead of posting complaints on the forum about how we don't follow your every suggestion.
 
 
 
Excuse me? Our answers are 'abusing' you?
 
Please. Get a grip. We're the ones actually improving the features you all are using, and what do we get? You publicly congratulating yourself for not donating money to the cause and complaining that it doesn't work.
 
Why do we work on this at all? Maybe because we bought the hardware, realized that it has limitations, and are working to improve it for our own use. We could certainly improve it and keep the improvements to ourselves. We're not selling a product, we're not required to push our patches upstream.
 
Unlike you, I don't go to internet forums of open source projects and whine that my expectations weren't immediately satisfied. I'm actually trying to improve things to the point where your completely unrealistic expectations ARE realized.
 
 
 
If you want to see "innovation" go use the Debian image from Xunlong: http://www.orangepi.org/downloadresources/ Do your own research before buying. You're presumably an adult, it's not our job to educate you before you spend money. We're able to spot marketing bullshit before buying, and adjust our expectations accordingly. I'd suggest you file this under a "learning experience" that not everything the salesmen tell you is true. At $10, it's a pretty cheap life lesson. We'd have a much better attitude if people like you didn't show up to lecture us on how we should be "innovating" more. The best thing you personally can do for innovation right now, is put away your Orange Pi Zero, stop posting stupid missives like the one above, and come back in 6 months.

This depends on your definition of "stability". These boards (most of them) will run perfectly stable on your desk (especially when using mainline kernel), but please keep in mind that these are the cheap development boards and not the industrial-grade PLCs. These are not designed to work in wide temperature range (especially below 0 Â°C), have minimal or close to zero power supply voltage filtering capability, minimal ESD, overvoltage, overcurrent, wrong polarity, strong EMI, dust, dew, moisture, etc. protection, and reliability may be affected by unclean shutdowns, so if you design any kind of hardware project, you have to know what these boards are capable of and treat them accordingly.

I don't understand you !!!
Who has "positive attitude" or "negative attitude" here, outside of YOU ...
The hardware design choice of Xunlong about eMMC on OPi0 is NOT an Armbian design choice !!! Armbian has NO relationship with Xunlong except to get some sample board to help community !
 
 
(I'm usually a quiet gentle guy, but here, please @igor, I'm getting out, if he fight, please BAN if forever)
What the FUCK ! As Volunteer, I'm should simply say to you :  GET OUT OF OUR FORUM !!! YOU'RE A SICK GUY !!!
 
EDIT : as I said eailer, STOP complain and become YOURSELF a CONTRIBUTOR !

I checked the first 10 pages of this subforum and found 11 threads describing different OPi Zero wireless related issues and questions, not counting this one and locked development related one. I think it's a good indication of what you should expect from this wireless module.
The thread that you posted in was related to the ongoing development and improvements of the driver, and after a dozen messages it turned into off-topic discussions, so it was closed for a good reason.
 
Also please keep in mind that Armbian is a non-commercial project too, not affiliated with Xunlong. We didn't make the board manufacturer use this wireless module, we didn't advertise any wireless related specifications or abilities like perfectly working AP mode, and constant unending spam of same questions and reports can make any developer regret that he decided to support this device.
 
Opi Zero it's still a good device for its price, just imagine that it doesn't have onboard wireless module. Want similar device with wireless? I think NanoPi Air may be a good alternative.

What if you already received best possible answers and you are simply not willing to accept the facts? In any case, do more research, try to understand the background if you wanna discuss it and stop abusing forum for your personal consulting service and we will treat you accordingly. Right @athamarmian?

Ok i do some performance check with copper plate ~30/30 mm and some small radiator ...

 
 

 

 
 
Now i need to think how to put there 40x40x30 mm radiator
 
After half hour with old cpu fan for lga 775

 

Perhaps, but right now I'd settle for a small miracle of reliable connections, which I'm guessing isn't happening based on the large number of a fore mentioned tx retries.

Unfortunately you're hoping like a lot of OPi Zero customers for wonders. Even if the driver will be fixed once XR819 won't be great.

We would all like better WiFi drivers. Unfortunately, all we have right now is what we got from ST-E/Allwinner and it's not very good.
 
52MBit/s is the PHY data rate, not the download speed. I'm getting at most 10MBit/s in testing (less than 1m from AP). The driver in use is xradio and can be built against the kernel sources (e.g. 4.9) so you have WiFi. Get it here: https://github.com/fifteenhex/xradio My modifications to the mainline cw1200 driver are enough to initialize the hardware, but the WiFi chip crashes when you try to scan or join a network.  
Since the cw1200 module in the kernel is almost identical to the driver from the Allwinner SDK, this means even if it worked with the XR819 (which it doesn't) the performance would be just as bad.
 
Honestly not sure why a driver for pre-production silicon with crap performance ever made it into mainline, but whatever...
 
 
We are working to improve the driver, but please realize:
We have no datasheet from Allwinner on how it's supposed to work None of us are paid to do this We all have normal lives with jobs and shit that take up lots of time  
So please be patient, and don't ask us when it will be finished. If you need a board with good WiFi, then that is not the Orange Pi Zero.
 
If you want to help, get Allwinner to release the datasheet so we don't have to guess how this thing works.