Power & Source of Big Ideas

Connect a debug cable to the T4 and see what is showing up in the output. If you don't have one, get one, they are cheap and it will help to diagnose what is wrong. The other option is to create a bootable SD image and hold down the BOOT button so that is boots from the SD card. If this doesn't work...
What else is in that directory?

This is T4 Android 8.1 from Gitlab?

This is the same directory and math is also a directory within this. Does this match up with your directory structure?

https://gitlab.com/friendlyelec/rk3399- ... gle/common
Under my 8.1 source, math is a directory.

What is in the text file?
What is here?

opendir failed: external/guava/guava-gwt/test/com/google/common/math: Not a directory
Yeah, remove the code you added and rename that old file and then do a clean and then rebuild. That will get you back to a working system. By the way, why do you need this SU version? I have found that the T4 build already has SU so you can do root via the debug UART or through ADB SHELL commands. I...
The LED wasn't blinking before the problem started, and I have since changed the OS, SD card, and power, so the common denominator is the firmware, I believe. Is there something in the firmware that might have triggered this? Looking at the schematic, the LED is driven by a GPIO pin. If this is ON ...
The debug serial port is your best place to see what's happening during the bootup.
The M4 I think is the same baud rate as the T4 which is 1,500,000 so use something like Putty to connect to the debug port.

I got caught out with this same thing too.
There are no other options. All of the other headers are outputs only. I actually like the 12V option as it avoids issues with voltage drops with a 5V supply, which I've seen a number of times. With the 12V input connection, it works from 9V to 14V without any issues. In fact, the datasheet shows 5....
Do you have access to a hot air re-work station?

It might be nothing more than a bad connection on one of the BGA balls.and a reflow of the memory chips might work. No guarantee but worth a try if you have access to one.
Any cheap USB to TTL 3.3V interface will work for this. Baud rate is 1500000 so need to use putty for this.

It will be the best investment you can make if playing with embedded Linux boards. You'll be able to track down the issue once you see the debug output.
Can you show us a picture of how this is wired up to the Smart6818?
Do you have a serial debug cable to see what is happening during the boot?

At least then you can find out where in the boot sequence failure is happening.
I added the capital versions and now it compiles without errors.

I've not installed it on my board as I need 8.1 for the time being.

Let me know how it goes for you and if it works on the T4 etc.
Some progress has been made.

Rename the Android.mk file in system/extras/su so that it won't be part of the build.

Now I get an error about the PLATFORM.pk8 file missing. I have not yet made copies of these in upper case.
Yes, there is another PRODUCT_COPY_FILES that creates SU into the xbin folder so we need to track that one down and somehow comment it out.

I've been searching for something to override the copy but can't find anything.
I bought this one and it was detected and I can save to it and read from it. I can't figure out yet how to boot from it but as storage, but it was detected with FriendlyArm Desktop.

NVME M.2 128GB MIDASFORCE LIGHTNING MAX SSD NVMe M.2 PCIe Gen3 x4
I am still trying to track this down. I can't find the product copy file for the existing su into system/xbin.
OK, following your instructions and I get the same failure message so not a setup issue.

Now to find out why.

I did notice that there is already an SU file in system/xbin so wondering if that has anything to do with it?
Thanks for your kind wishes. I am getting better every day and back working from home. I had a look and have not yet attempted to try and build this into my system. I will get around to this during the rest of the week. I wanted to check if the binary that is on the SU git page is compatible with th...
Hi there, I too use the T3 Plus board but for commercial projects. I run Android 5.1 on the current designs but I also have 7.1 in development. It's not quite ready to use yet as issues with getting SELINUX to be in permissive mode on startup. The boards are fitted to a motherboard via Samtec header...
The best place to do this is in u-boot as it will be the first thing to run. You can do this in the kernel but that runs a little later. To guarantee a GPIO is low or high at power up, the only real solution is a pullup or down resistor.
You can use a wakelock to turn on the screen but to turn it off will require system app access using the system keys to build your app. Loads of stuff here about what you are trying to do but the system app is the only real way. https://stackoverflow.com/questions/9561320/android-how-to-turn-screen-...
Which OS?
I've just gotten out of hospital so sorry for the delay.

I'll follow what you did and see what happens to my build.

Are there any files to download for this?
I am looking at the .mk file and there is a su file in the directory indicated above. Are you trying to copy another su over this? Could that be the issue?

Can you detail the changes you have made and I'll try the same here?
I also needed a front panel switch for power and the only way to do this was to solder 2 wires onto the pads of the existing switch on the board. There is no external power connection for the T4. This is something FA should consider for all future boards as once installed into an enclosure, the boar...
According to the schematic, there are MOSFET drivers on this to switch the fan ON and OFF via GPIO2 which is also marked as PWM2 at the same time. Not sure if the kernel is already driving this as ON and OFF or PWM but it is possible to control the speed with this for a basic 5V powered fan if you h...
I've downloaded the GITLAB repository and built it first without any changes and it completed in a few hours. I am running Ubuntu 12.04 64 bit as legacy because I also have an older Android 5.1 version that doesn't build under higher versions of Ubuntu although 8 and 10 should build with a later ver...
My apologies, what I should have said was that it is not the PCI Express slot with the USB. It's an M.2 slot instead which is not the same as the card edge on the SIM7100E-PCIE module with different key position and that version has USB and SIM card connections. Use the SIM7100E-PCIE card with a USB...
The slot on the rear is not PCIE and it has no USB connection either. I used it via one of the USB ports and a PCIE module to USB convertor board. I've not yet seen Android 10 driver from SIMCOM and only managed to get this working with Android 8 although I have seen a number of websites offering An...
This is the partmap for Android 5.1 on the NanoPI3 boards. It works but the first entry seems to be too long and actually ends up 0x200 into the bootloader area. The start of 0x200 and length of 0x8e00 means that the end is 0x8200 and the bootloader starts at 0x8000. Older versions of this file are ...
The W500 has the same resolution as the old obsolete S430 LCD with 800x480 resolution. I have added the W500 timing and setup to the kernel and u-boot and the display is working but there are no home, back or recent apps buttons on the LCD display. There is only a blank space where they should be. A...
Anyone know where to get the Android 7.1 Google Apps to build into the OS ?
Looking at the schematic UART1 and UART2 are the only 2 available. UART0 is connected to the Ethernet port.

UART2 is the debug port but UART1 should be available via the GPIO header. What is the ownership on the /dev/tty ports?

Is there a ttySAC* port?
I have a custom Android 5.1 build and I can flash this to an older T3 Plus board and it runs. When I try to do the same on any newer board (I have 6 of them doing the same) it reports "Failed to load BL33" in the debug output. Both boards are marked with the same revision number. The only ...
At 155uA you should be able to get at least 50+ days out of the 240mA rated CR2032. In saying that, the standby current is still too high for an RTC in standby.

What ambient temperature is the device operating in?

PS. I used this calculator.
https://oregonembedded.com/batterycalc.htm
How much current do you need to draw for your external devices?

The schematic will have the IC that provides the 3.3V so you can check this and guess at the power available.

I would say that for anything more than 100mA you should use an external 3.3V regulator.
The best solution is to hook up a USB to TTL convertor and monitor the debug UART output. This will indicate where in the boot sequence things have gone wrong.
I have a T4 that has FriendlyDesktop installed on it and running my home automation system after moving over from a Raspberry PI that has done the duty for many years. The T4 is much faster for web interface. I have purchased an NVME M2 SSD with 128GB of storage and I would like to use that as the p...
Which OS are you using and do you have the drivers for the 8223A installed?
I need to update to the latest Android build and try running the eDP display again. I've not used it for some time with the HD702 displays. I a using the 11.6" E116 display and that is rock solid with the T4. No issues after running for hours.
The documentation for both can be studied to determine if the pins are the same. I suspect they are and the difference is in the board layout. In fact, looking at the wiki and doing a side by side comparison, the connections are identical.
Although FriendlyArm indicate open source, the only real open part is the schematics and software. To my knowledge, they have never released any PCB design files. You will basically have to create this yourself with your own PCB design suite from the schematics they provide. A daunting task. The rea...
Which display are you doing to use with it? I have a T4 with HD702 and booting Android, it consumes up to 600mA during bootup. Once the desktop is present, is idles between 320ma and 400mA. I am measuring this with a 12V bench power supply with digital current display, GWInstek, model GPS3303. On an...
If you have a USB to TTL cable, hook it up to the debug port. It is the best way to see what is happening with your board during the boot sequence.
Under the source for the Android build, if you search for .ko do you find any files? There should be at least a file called mali_kbase.ko in /vendor/rockchip/common/gpu/MaliT860/lib/modules in the source tree. In the /vendor/rockchip/common/gpi directory there is a MaliT860.mk file and opening this ...
Can you explain in more detail what you did?

Is that an output error from the build or something esle?
Can you look in /vendor/lib/modules/wifi and see if the bcmdhd.ko file is present?

When I list that directory, I get these files. You mentioned before that the .ko files were not being built.

8188eu.ko 8189es.ko 8723bs.ko 8723cs.ko 8822be.ko
8188fu.ko 8189fs.ko 8723bu.ko 8723ds.ko bcmdhd.ko