FriendlyELEC-Forum

Just a thought. These boards are sold for development and you get the source code for them so why not compile in the CEC support that you need? I've spent many weeks in doing that very thing with Android to add GPIO, I2C and SPI without needing access to the platform keys. I am not there with SPI as...

Information is in the Wiki for the T4. Here is the direct link. It is in Chinese so use Google Translate. http://wiki.friendlyarm.com/wiki/index.php/Modify_T4_PWRON You need a 300K 0402 resistor and a 1uF/16V 0603 capacitor. I hope your eyesight is good and you have a small tip soldering iron as tho...

As per my other post on this, the only way to flash the eMMC is via SD card.

http://wiki.friendlyarm.com/wiki/index. ... ge_to_eMMC

It works fine. I do it on a daily basis when I am developing the Android OS.

Did you copy the files to the android7 or android8 directory in the FriendlyArm partition? Do you have a serial debug cable? That will make testing a lot easier as you will see the boot process and why it is failing. Without this cable, you are totally blind. Even if the image in the directory is wr...

I have rebuilt the OS to change the GPIO header to use SPI1 instead of UART4. The device shows up in /dev/spidev1/0 and I can open and close it, send ioctl commands to configure it, but I cannot get it to accept writes. I get the following error in the debug terminal. rockchip-spi ff1d0000.spi: spi ...

Pretty much although the build system for 8.1 is really nice with the kernel and u-boot all included in the same directory and a very nice build script to deal with it. You can build u-boot and the kernel first and then Android. The script takes care of copying each kernel and u-boot images to the c...

OK. Assuming you are using Android 8.1 build, locate the eflasher in the download and write this to your SD card. It will create 2 partitions and one will be named FriendlyArm and have an android8 directory. Follow the instructons on the wiki. All the information on how to make the SD is there. 13.3...

Copy the final build outputs to the SD card. For Android 8.1, they go in the android8 directory. Just overwrite the old files. Inserted into your board and power up. It will flash to the emmc. Then shutdown and reboot without the SD card. All the information to build the Android source is under the ...

Just a quick update. I found the following would list what each GPIO was currently being used by: cat /sys/kernel/debug/gpio gave this: gpio-35 ( |camsys_gpio ) out hi Seems that the camera is using this GPIO which seems a bit strange as that pin is not connected to any of the camera connectors, onl...

When I use the SD card to flash the emmc, the SD card contains an Ubuntu OS that has a special program from FA that runs, and then you can see on screen what is happening. It should boot with an interface. The FA logo should appear at initial boot. The LED will flash faster when the OS is being writ...

Follow this to use create an SD that you can write to the emmc. This can also be used to flash your own custom Android builds.

http://wiki.friendlyarm.com/wiki/index. ... nd_SD_card

I can't get code to export the GPIO1_A3 pin on the T4. GPIO1A1 and GPIO1_A4 exports without any errors. In fact, all of the other GPIO pins on the header can be exported. I tried from the terminal in kernel space with SU but still doesn't export. The schematic for the T4 shows that GPIO1_A3 only con...

I want to be able to add additional external storage to the T4 but when I plug in a blank SD card with FAT32 format, the system fails to boot.

How can we add SD card storage to the T4?

Does this help?

http://wiki.friendlyarm.com/wiki/index.php/I2C

The only difference is the USB to SERIAL IC used. The CH340G is what FriendlyArm use on their own boards but any of those will work for you. Just be sure to have the correct driver installed for you OS.

Do you have TTL to USB serial adapter?

Seriously, this should be top of the list of haves for anyone working with modules such as this. It will give you much more information about what is happening during the boot cycle etc.

Hi Tom, I've not used any resistive driver with Android but I do know for usre that you do need to calibrate them to get the correct coordinates to map screen to touch panel. The ADS7846 is a resistive driver with SPI interface and you might find a driver for this in the kernel. Might be worth seein...

I have 2 of them and the LCD is bonded to the PCB with some kind of double sided tape. Unless it can be removed, it would be impossible to see if there are any other indications on the LCD panel itself. The technical drawing of the LCD has had the manufacturer details blurred out. :( I would add tha...

I've created a 3D model of the NanoPC-T4 and put it up on GrabCAD if anyone is looking for something like this. It's not dimensionally accurate as I had to find 3D parts for the connectors and they are not the exact ones but the PCB and the holes are accurate. It should be good enough to help if you...

I shuuld that I set the Realtek as the wifi vendor in wfi_bt_config.mk

Code: Select all

#BOARD_WIFI_VENDOR := ap6212
BOARD_WIFI_VENDOR := realtek
BOARD_BLUETOOTH_VENDOR := broadcom

Android 7.1 source has an option to build with the Realtek RTL8xxxxu driver which supports the RTL8192CU wifi USB module but I am not able to get this to work. I get the following error in the debug output. [ 113.926666] usb 2-1.3: new high-speed USB device number 4 using exynos-ehci [ 114.023333] u...

Turns out that the latest SD card format uses exfat for the eflasher and although this can be used to flash Android 5.1 to the emmc, it can't be detected by Android.

Installing an SD card with fat32 format works fine.

You should be able to just use a suitable SD eflasher image to re-program the emmc.

Flash an SD card with the correct eflasher image and then boot from this to reprogramme the emmc.

I have 2 NanoPC-T4 and I used eflasher from the SD card to program the emmc. Works without fail. I used Win32DiskImager to create the SD card from the image downloaded from the FA website. I've installed Ubuntu as a test but currently using Android 8.1 on them. You u-boot shows that it can't find th...

mrigendra wrote:
3. uart (115200 bps) shows garbage

This generally happens when you don't have a ground connection. Double check for this.

It should be 115200, 8, NONE, 1

I used the latest SDflasher to programme the emmc of the Nano PC T3 Plus with my custom Android build which has been working for a couple of years now. The latest boards I received from FA did not detect the SD card. I found today that when I try to mount them, the following error appears on the deb...

I use a JNI to do this. Here is the serial port file for you to see how it's done. /* * Copyright 2009-2011 Cedric Priscal * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the L...

I am trying to debug a SPI application but think there might be an issue in libfriendlyarm-things.so. Where is the source for libfriendlyarm-things.so? That library is not open source. I have GPIO and I2C working using a JNI. I've not needed SPI but I did find this Android SPI code you might be abl...

Glad to hear it. It's just going to take time. I am getting PCB's made just now and normally 3-4 days, but now on 7th day and still not shipped. It was expected but I am grateful to the Chinese people for slowly getting things back up and working. It's a tough call. It could be a lot worse.

My recent order of Nano PC T3 Plus boards has come preloaded with Android 7.0 and I am trying to put Android 5.1 but getting boot issues and kernel panics. I used the latest eflasher for Android for Lollipop from 27 Dec 2019 and it boots into Android 5.1 but has portrait mode. My custom build runs i...

The date notification disappeared the other day so they may be back to work in a limited way with less workforce. The same with other Chinese based companies that I use. They may be overwhelmed with orders placed during the initial Chinese New year and loads of emails so you'll probably have to give...

PS. I see you posted this in the RK3399 forum so let's work on this for the T4 or other boards based on this processor.

Not much from FA. They have done a few upgrades and it would be nice if they could write up a wiki page on what is required to create a version upgrade. ;) I have been looking at how to jump to Android 9 and have 5.1 and 7.0 source so I was trying to figure out how to do this. The first part I think...

To get this to work, you need to make sure you select the correct SPI interface. Next up is working out the GPIO and changing the source to map it to the RK3399. The WiFi has a good section on how to deal with mapping GPIO names to GPIO pins. The Raspberry PI is for the Broadcom processor and hence ...

Everything looks good in the output.

I see you are running Android on this.

If you have a PC running Ubuntu, it is quite easy to build your own custom OS and get rid of the stuff you don't need. All depends on what you are wanting to use it for.

When you connect to the board, do you just connect GND, RX and TX?

You don't need the 5V connection as your board is powered elsewhere. Better to leave this disconnected to avoid shorting power supplies.

It all sounds like a ground issue. I assume you are using a 3.3V TTL serial interface to connect to the debug port?

You need to use a good quality power supply. The many cheap ones may say 5V 2A but rarely output much more than 1 amp before the voltage drops.

Meanwell do some very good power supplies that work well with the FA boards.

Gibberish usually indicates a missing ground connection.

I think the Quectel modem is supported out of the box with the T4 and Android 8. If you want to support another modem via USB, you need to build the OS to include the RIL for that modem. There is a generic RIL but I've never gotten it to work. Android doesn't support any modem out of the box and you...

Which OS. I have the SIMCOM SIM7600E-PCIE module working with the T4 under Android.

Best way is to connect to the debug port and look at the boot output. This will tell you what is going wrong.

What have you tried? Your post is worthless without any information.

I have found that the latest SD FLASHER can now selectively only flash partial updates such as kernel and u-boot so that may be a way forward.

If the HDMI display you are using has native resolution of 800x480 and has the EDID connection with the details, it should automatically adjust itself.

You also don't state which OS you are using? The HDMI settings should also be in the Wiki.

As long as the LCD Module itself is still available, I am sure for an order of 350, FA would make them for you. It would be nice if FA issued some form of support on their website when a design is due for obsolescence and give us time to prepare for it. Instead, they just drop the item from the webs...

The debug port provides 5V but the actual voltage levels for the RX and TX lines are 3.3V. There are current limiting protection resistors inline but best to use 3.3V levels. VCC_IO is wired to 3.3V in the schematic. The baud rate is likely why you didn't see anything.

Your only option to get this working is to either find an SPI based driver for the XPT2047/ADS7846 and try getting this to work on your board or you may need to write your own if none exists. The ADS7846 is very easy to use and once you have calibration done, it will work well. Once you configure it...

I am working with Android 7 for the NanoPC T3 Plus and I can build it without error using custom u-boot and custom kernel. I need to enable the Realtek WiFi drivers and if I change the following line in wifi_bt_config.mk from: BOARD_WIFI_VENDOR := broadcom to: BOARD_WIFI_VENDOR := realtek And then t...

I assume you are running Ubuntu on this board as you posted in the Ubuntu forum?

The XPT2047 is the same as the ADS7846 so you'll need to try and find a driver for this or roll your own. A search does find some Raspberry Pi versions.

I just checked out the manual and the LCD connections to the PI show that the touch controller is via the SPI interface but I can't make out the IC they user but I have a suspicion they are using the AD7843 or similar. Can you read the part number on the SSOP part next to the GPIO connector? I think...

Search found 387 matches