I feel like I had to use a specific installer, or change a setting, to get Ubuntu installed on my old board. But ,if so, I can't recall what I did. So... any assistance/advice would be greatly appreciated! I'm also open to Debian or Ubuntu Desktop, or whatever... but I don't want to just keep shooting blind, if i can help it.

I originally setup the Up Board with an IP address etc. I was aiming to use it as a headless Linux box. I may have disabled the video output, if that was an option.

So now I want to use the Up board for a CCTV app. I am trying to install a new Ubuntu OS. I created and plugged in a bootable USB with Ubuntu for installation. I connected to a keyboard and display.

When I boot the Up, there is no video output. When I try and connect via Ethernet, I can't ping the IP address of the Up.

I have looked in the Wiki to see if I can find an answer.

Is there a way I can force the Up to boot to the USB?
Is there a way I can do a factory reset of the Up?
Is there something else I can try?

I have 24V connected to a voltage divider (R1=68k, R2=10k) and the output connected to ADC0/GPIO4/PIN7.

Via sysfs, I export gpio4, set direction to in, and connect the output of the voltage divider.

When I read in_voltage_raw (via sysfs /sys/bus/iio...), I get "7" or "8" no matter what, unless I ground it, which I get "0".

in_voltage_scale is 12.890625.

The voltage at the ADC0 pin is around 3.2 so I am expecting (3.2*1000) / 12.89, or 3.2/255, or something, but this thing just reads the same value regardless if its 1.2V, 2.4V at the pin or 3.2V.

How do you correctly setup this ADC0 pin? Do I need to drop the resistor values to 6.8k/1k? I don't know what the desired current rating for this pin is, and I cannot find any setup information to know if I am correctly exporting, writing direction, etc or if there are more steps I need to take to configure ADC0.

e.g. RTC Battery is necessary to maintain mmc data during no power? I see my Upboard right now, but there is no connector for RTC Battery.

Name: UP Board Series
BIOS: UP-CHT01 R0.T(UPC1BMOT)
CPU/RAM: x5-z8350/4GB

I, unfortunately, overvoltaged the board with 12v. I was able to boot a couple of times but now the screen appears completely black all the time when I power it. I noticed that when I booted the consumption was 2Amps and now it just consumes 1 amp.

I found two questions about the same topic https://forum.up-community.org/discussion/2069/now-that-i-fried-my-only-up-board , https://forum.up-community.org/discussion/comment/8806#Comment_8806 and it seems that there is not any possibility to recover the board.

I am trying to read how to (somehow) recover the information in the eMMC. is it possible? I hope there is a way of entering to some recovery mode with minimal usage to read the eMMC content.

Any advice will be appreciated.

EDIT: I am trying to move the post to the right forum but I cannot, I am referring to this version of UpBoard https://www.mouser.es/ProductDetail/AAEON-UP/UP-CHT01-A22-0432-A11?qs=XeJtXLiO41S0JpGxYUwwTg==&vip=1&gclid=Cj0KCQjwpfHzBRCiARIsAHHzyZp5Xa62d5NyrGmaaJTqPYxNenGVujjHTFcOzXlk02nNI2dJcbBT8uQaAuaZEALw_wcB

does anyone else encounter such a behavior? And more important, knows what it causes?

We have build around 80 customer advertising displays with the Up Board. Because it runs Windows, a hardened custom IoT build but nonetheless Windows , it has a nightly reboot scheduled. Sometimes the UpBoard, in some systems, hangs at the password screen (before you can enter the BIOS) that shows up after you hit F11 in the boot phase. This systems doesn't have a keyboard attached.

The Problem is that we can't repair that from outside, we have TeamViewer installed but that obviously doesn't work at this state.

even with no USB keyboard connected there seems to be an issue as if the down arrow key is stuck. This issue only seems to be active during booting, e.g. GRUB boot entry selection or while selecting the boot device.
It dows not occur in BIOS or when OS (Windows / Linux) is booted.
If I connect an USB keyboard I can use the cursor keys and work my way to the correct entry... very strange issue and I'm wondering what I'm missing here.

Best
Matthias

working on xrdp, and cpu is never full used.
I don't use vision plus, for now (but it's conncted)

when i'm working on it it oftens reboot. It's really boring !!! any idea ?

I am using an UP board (UP-CHT01-A10-0216) with BIOS version UPC1DM25. The device is meant to be deployed and function without any user input. We have Ubuntu server 20.04 LTS running and it is the only OS that should be booted. For IP protection, we wanted to prevent people from booting a live USB and copying the flash from the UP board. So we enable BIOS user password to protect access to the BIOS. When the BIOS user password is enabled, the device does not boot automatically into the OS even though the OS is the only option to boot into in the boot order configuration. It halts for BIOS password before the OS is booted - thus requiring user intervention.

Can you recommend a way around this to prevent access to BIOS but also boot without user input?

This month, I bought new upboards and I did same; I installed ubuntu 20.04 and kernel upboard 5.4.0-1. But there are is some differences:
yesitis@upboard:~$ uname -a
Linux upboard 5.4.0-1-generic #0~upboard5-Ubuntu SMP Fri Jan 7 11:53:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

You can see upboard4 => upboard5

The modem uses ttyUSB4 serial com for AT commands. My program (C code) communicate well on upboards 4 but no byte received on serial com on upboards 5.

Do you have an idea?

Thanks.

I have tried a circuit with just the DC-DC converter and with the converter's recommended EMC filter, both gave the same issue of only allowing the UP board to read one USB device.

Do you have any idea of what could be different power-wise between the AC adapter and the batter + step down circuit that can also deliver 5V 6A? Or any idea of what to test to troubleshoot this issue? Need to have the UPboard read these two USB devices on battery power so it's not tethered to a wall plug, so if anyone knows what I could try to fix this issue, I'd greatly appreciate it.

Here are the components I am using:

UP board: 1x UP Board 02/32 (2GB RAM and 32GB storage): https://up-shop.org/up-board-series.html

9S 25C 4400mAh LiPo batttery: https://www.thunderpowerrc.com/collections/4400-mah/products/tp4400-9spx25

5V 6A DC-DC converter: https://www.digikey.com/en/products/detail/cui-inc/PDQ30-Q48-S5-D/6165430

Pressure sensors: https://www.sensorprod.com/pdf/tactilus_shoe_insole_high_performance.pdf

UPBoard AC adapter: https://up-shop.org/up-squared-power-supply-5vat6a.html

Does anyone know what is causing this or is there a way to fix it? I'm sure no water gets into this board. I have tested it many times, no problem. But there was a problem in this round that made it impossible to continue the work.

I tried following this link

https://forum.up-community.org/discussion/908/fix-wont-boot-no-hdmi

but nothing changed.

Does anyone know what is causing this or is there a way to fix it? I'm sure no water gets into this board. I have tested it many times, no problem. But there was a problem in this round that made it impossible to continue the work.

Sep 23 15:05:48 UP-CHT01 kernel: [280361.789559] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400e00
Sep 23 15:09:32 UP-CHT01 kernel: [280586.520555] INFO: task jbd2 / mmcblk0p2-: 217 blocked for more than 120 seconds.
Sep 23 15:09:32 UP-CHT01 kernel: [280586.520564] Tainted: G OE 4.15.0-37-generic # 40 ~ upboard07-Ubuntu
...
...
...
Sep 23 15:15:48 UP-CHT01 kernel: [280961.822885] mmc0: Card stuck in programming state! mmcblk0 card_busy_detect
Sep 23 15:15:48 UP-CHT01 kernel: [280961.878891] mmc0: Tuning timeout, falling back to fixed sampling clock
Sep 23 15:15:48 UP-CHT01 kernel: [280961.879235] mmc0: cache flush error -110

Info about eMMC from dmesg:
[ 2.493106] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA
[ 2.592665] mmc0: new HS200 MMC card at address 0001
[ 2.599631] mmcblk0: mmc0:0001 DA4032 29.1 GiB
[ 2.601903] mmcblk0boot0: mmc0:0001 DA4032 partition 1 4.00 MiB
[ 2.604088] mmcblk0boot1: mmc0:0001 DA4032 partition 2 4.00 MiB
[ 2.606099] mmcblk0rpmb: mmc0:0001 DA4032 partition 3 16.0 MiB, chardev (243:0)
[ 2.612714] mmcblk0: p1 p2
[ 3.453619] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.382965] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro

What could be the cause of the problem and what should we do to solve it?

Every fix I could find has been implemented. The PPA packages are installed. I'm not even sure why sane defaults aren't the stock behavior on BIOS releases, which require archaic update mechanisms instead of selecting a file within the BIOS, or using fwupd.

I still get random and non-random crashing on all boards. Firefox was the included browser. Crashes. Sometimes the Application menu crashes. Sometimes the units reboot multiple times before successfully "catching" and actually booting. This is considered progress from having a non-working reboot or shutdown mechanism, requiring additional BIOS settings.

I wouldn't know if later kernels fix any of this, as I am told I have to use a kernel from over a year ago in order to boot with GPIO and I2C intact because apparently this is a better idea than breaking it out into userspace.

Does anyone maintain a functional ISO, free of these issues that wouldn't be acceptable on a consumer tier tablet of equal cost? Has anyone actually fixed all of these issues?

The circuit in pin 7 works as expected. It acts like a floating input during boot and I can set the output state at boot time using the jumper.

Pin 5 however stays at 1,5 volts during boot and it pulls the voltage at the transistor base to 0,7 volts regardless of the jumper setting. Voltage stays at 1,5 volts even after the pin is exported. When I configure it as output I can write it high or low and the voltages are 0 volts and 3,3 volts as expected. I have already tried to disable everything I2C related from BIOS. How can I make this pin act as a floating input?

Windows iot enterprise LTSC ver 1809 build 17763.1852
Cores temperature are all below 55°C!

See attached screenshots.

Thanks a lot for helping
Best regards,
Alessandro

Model upboard 1

I unsuccessfully dropped the upboard and the quartz resonator (as I suppose, it's crashed) upboard no booting, the only part that is damaged is it. I just can't find its specifications by its marking.

I found a photo on the Internet, indicated with an arrow on the part that was damaged.
Who can link to a part or tell its specification?

I have a problem installing the drivers. I have windows 10 installed and running but while installing the driver package it gives me an error.
Looking around on the forum I see different people having had the same problem (https://forum.up-community.org/discussion/717/installation-of-win10-64-step-1-drivers-fails)) and being able to solve it by removing the spaces in the 'step 1' folder name.
Unfortunately this doesn't work for me.
I saw someone else having had succes by updating the BIOS, so I gave that a try as well, but I also seem to not be able to boot into UEFI, even though having followed the steps.

Is there someone who can point me in the right direction?

Thanks!!

State after G3 set to S0. Behaviour:

• After a power failure, when power comes back the board correctly boot-up

State after G3 set to S5. Behaviour:

• After a power failure, when power comes back the board powers on (blue led ON and fan running), 3V and 5V present on pin header, most of peripherals powered, no boot-up until button is pressed. It never remains off.

I expected that after power fail, the board remains totally off, and when the switch is pressed it comes up and boots.

Am I wrong?
Did somebody else experiment the same behaviour?
Is it related to a specific UEFI BIOS version?
Is there any way to "trick" the behaviour and keep the board totally off after power fail?

NOTE: The same setting on UP-COREboard, instead, behaves differently and the board seems to remain off until button is pressed, that is what i need on UP-BOARD.

The scenario where the board should operate in my project requires that the board remains off (even if power is plugged) untile a control until somebody press the button.

Thanks a lot for the support.
Ale

I have the problem that the board powers up only to show a blue light. In this thread other people also try to deal with the issue:

https://forum.up-community.org/discussion/2223/no-boot-just-blue-led#latest

Can I use a CH341A based flasher and a SOIC8/SOP8 test clip to re-flash the BIOS chip with flashtool to try to fix it? The BIOS chip has a label attached which reads "62UP C1B0" which was probably the BIOS version the board came with originally.

If yes, can I just use the "UPC1DM17.bin" file directly? It is exactly 8MiB in size, so that sounds valid.

Regards,
P

I am using an Up Board(UP-CHT01 R1.7 UPC10M17) and trying to install Windows IoT Core onto it.

I am following the instructions from here: https://docs.microsoft.com/en-us/windows/iot-core/tutorials/quickstarter/devicesetup#flashing-with-emmc-for-up-squared-other-intel-devices

I am using the UPBoard_WinIoTCore_RS5_17763 flash.ffu file, and have created a bootable USB drive.

However, I cannot boot onto the USB drive. The Up board detects the USB drive, and I have set it to boot from it. Whenever I press F7 and select the USB drive it does nothing, and cycles back to the same options screen. I have removed the CMOS battery multiple times, and have recreated the bootable USB.

I noticed that my BIOS version was above the options given on the Up Board download site(version R2.1). I then installed R1.7 to see if that would fix the issue. Is it possible that installing Windows IoT core on the R2.1 version before bricked the Up Board? The first time I attempted to install the OS, nothing happened except the board constantly rebooting itself.

Thank you for the help.

I figure this is a driver issue with the realtek 8111 nic. Can't seem to figure out how to install the driver though.

Does anyone know how to fix this without internet?

Tried it with another up board power supply, still shuts off.
The fan doesn't appear to be spinning on start up, not sure if thats normal or not.

whats wrong?

Sur l'article d'installation du kernel upboard pour ubuntu 16.04, j'ai remarqué une erreur dans la partie 2 Install Ubuntu kernel 4.15.0 for UP from PPA on Ubuntu 16.04. Le code suivant a été mis vers la fin:

sudo apt dist-upgrade -y
sudo reboot

alors qu'il aurait fallu mettre:

sudo apt dist-upgrade -y
sudo update-grub

Si vous pouviez modifier cela ca serait génial !

Merci d'avance.

Thank you in advance.

I am using UP Board and 2UP HD camera connected to the same SBC. It is showing me the camera devices in /dev directory by name video0 and video1. But after some time device names are getting change like video2 and video3. Because of that I am not able to use cameras So please let me know how to solve this issue.

Regards,

Hariom Singh

system:

HelloBlinky
https://github.com/ms-iot/samples

RHPROXY Problem:

https://forum.up-community.org/discussion/4120/spi-gpio-support

https://docs.microsoft.com/en-us/windows/uwp/devices-sensors/enable-usermode-access#verify-that-rhproxy-is-present-on-the-system

DefinitionBlock ("ACPITABL1.dat", "SSDT", 1, "MSFT", "RHPROXY", 1)
{
Scope (_SB)
{
Device(RHPX)
{
Name(_HID, "MSFT8000")
Name(_CID, "MSFT8000")
Name(_UID, 1)

        Name(_CRS, ResourceTemplate()
        {

            GpioIo (Shared, PullNone, 0, 0, IoRestrictionNone, "\\_SB.GPO0",) {36}  
            GpioInt(Edge, ActiveBoth, SharedAndWake, PullNone, 0,"\\_SB.GPO0",) {36}
        })

    }
}

}

https://forum.up-community.org/discussion/4120/spi-gpio-support

make ACPITABL.dat and load

Problem ：12
error code：0xC0000034
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-normal-conflict

South Bridge Settings are showing - eMMC: Unknown TB2816 ACE3823 (14.6 GB)

Is there a fault with the eMMC as I have never had this issue before

Shit happens. Please help.

Thanks and Regards,
Hariom Singh Kushwah

I got these error messages when rebooting today.
I can still login the system, is there any problem of Upboard?

In some situations, the board turns off. It seems to me that this is due to too high power consumption.

So my question is whether there is a possibility to monitor the power consumption so as to catch the power consumption at which activities are too high. Is it possible to use some kind of logger?

We use UpBoard with an HDMI 1024x600 screen + touchscreen.
Operating System "Ubuntu 16.04.5 LTS (GNU / Linux 4.10.0-42-lowlatency x86_64)"
Somewhere once a day, the image on the screen disappears and the screen turns to gray background.
The following error message appears in the syslog:
[drm: intel_cpu_fifo_underrun_irq_handler [i915]] * ERROR * CPU pipe C FIFO underrun

Such a situation occurs on more than 10 devices.
It seems, the probability of the bug increases when the CPU usage increases.

Sometimes the screen is restored after manipulating on the touchscreen. However, rebooting is needed in most cases.

Are there any known fixes except for the one where you add cstate=1 in grub?

Running ubuntu 16.04

Provisioning would just use the barcode sticker on the device. However, there are 2. A larger one on the GPIO header and a smaller barcode sticker on top of the USB port.

Using dmidecode -s system-serial-number, we get the number listed on the smaller barcode.

But I haven't been able to find how to access the s/n listed on the GPIO barcode which seems to be the one listed on all the upboard order forms and receipts. Does anyone know where/how to access that SN? (mine typically begin with C1XXXXXX)

My board began to work and seemed to be fully functional. A few hours later and its back to not working

Power light comes on
Fan spins
processor works, it at the very least heats up
the 3 LED's below the USB ports work

I have no video out over HDMI, no ethernet status lights, or power to my keyboard. There appears to be no physical damage to any part of the board.

I am using a 5v/4A power supply and have followed as many troubleshooting steps as I could.

We have encountered a problem with around 10% of our ~60-80 "WiFi kit for UP". These Systems (UpBoard 4/32 Passive + WiFi kit for UP) works normal till a point where the internet connection is lost. A closer look at the network connections reveals that there is no WLAN Network/Chip Windows can see (only Ethernet is left).

The solution: Sometimes a simple reboot works, often it needs 3 or 4 of them (including power cut), and from time to time the power needs to be cut for several minutes (obvious I can't test this perfectly but my Testsystem right beside me had this problem yesterday and ~5-10 seconds wasn't enough, I thought the WLAN Chip was broken, I tried it finally for around 5 minutes and now it works again). BIOS is at default Settings.

Did you know of such Problems? I could believe that 1-5% of the modules could be faulty if they were cheaply made in China, but 10% (or more, we couldn't get the exact number if customers reboot it without telling us)!?

What I've tried:

• When I hit F7 when the system is booting up, it doesn't display any options except "Enter Setup"
• I've tried updating the BIOS, however I'm unable to load up the EFI Shell from the filesystem device

I contacted support to submit an RMA, however I received this as a gift so they will not let me make a claim.

Do you have any suggestions?

This is Hariom Singh. I am using UP board with 4 GB RAM and 64 GB memory with Ubuntu 18.04. I have installed tensorflow 1.14.0. When I am importing tensorflow ( import tensorflow ) that time I am getting error " illegal instruction ( core dumped )". I tried this with tensorflow version 1.13, 1.6, 1.8 and 2.0. I am getting same error.

For tensorflow 1.5 I am able to import tensorflow but when I am running my program (object detection )that time it is showing error "No op named NonMaxSuppressionV3" in defined operations.

So please help me how can I resolve these errors.

Thanks

The eMMC was changed under this PCN. We notice that image across devices with different eMMC brand may brick the board. This issue seems to be caused by an issue in the eMMC controller embedded in Cherry Trail SoC. We have escalated to Intel for further analysis and resolution.

As it might take quite some time for Intel to provide a fix. The suggestion is to create a new image based on new eMMC.

In principle, we suggest you create a new image while there is PCN on the product, especially on eMMC to avoid similar problems.

The product still provides the same functionalities as it should be today, and we hope this solution could be helpful.

Problem I mentioned is with HDMI signal split into two monitors. I use UP-CHT01-A20-0464 with Windows 10 and HDMI signal splitter. When computer is booting up, the signal is being provided for both screens, but after a full start of WIN10 it goes off and monitors go black as no signal is being received. Is it because of the WIN10 driver or maybe something else ?
Is there a way to solve this ?

Next, from time to time blue screen is being displayed after Windows 10 start. What can be the reason ?

Regards,
Pawel.

I was able to find ubilinux3 iso and used that to download a base image. When trying to update packages, apt couldnt download anything ubilinux related, logging that ubilinux.org was not found.

I am wondering if the ubilinux website if something is going on in my network, or if something is going on with ubilinux website/downloads.

Has anyone else had trouble the past couple of days/weeks?
Thanks.

We work in cooperation with the VIT company to manufacture industrial "Outdoor Box" PCs used for the running neural networks near the data source. As a basis, we use an UP board and during operation, we faced a problem that the device stops turning on after a certain number of shutdowns to restore power. To turn on, you need to manually press the Power button. Actually the device is in the “half on” state, the power indicator is on, but there is no power on the USB, and the board does not boot. This is a big problem for us, because the device must be dismantled and disassembled to access this button.

Marking on board:
UP-CHT01
1907UP6402
Rev:A0.3 0 0

BIOS version: 2.17.1249

And now i want to install Windows 10 on it, but Windows 10 needs more Storage. Does anybody know what I have to do?

Does not even wake from sleep.

I saw the moderator says the Up Board supports WOL but i don't see it.
And there's nothing referencing WOL in the BIOS.

Any help is welcomed.

Best regards,
Chris

I recently acquired an UP-Gateway at the office and installed KUbuntu 18.10 on it. I tried to install the Ubuntu 18.04 and 16.04 previously but encountered some issues and had to go on 18.10 for some reasons that i can't really remember.

So now the issue is that sometimes the reboot process does not reboot completely, instead it just shuts down the UP and there's no way to restart it except by unplugging the cable and plugging it back.

Is there a way to avoid this ? As we're going to have those UP-Gateway that can be unaccessible we'd like to have a safe way to reboot the UP.

Thanks !

i have tried holding power button nothing happends.. blue light is steady and fan is moving
and also i tried removing battery and all nothing is happening

please help me

I am powering it through power jack connector with 5V4A. I have already tried resetting the BIOS by removing the RTC battery for some minutes and plugging it pack.

I wonder if there is any hardware test (e.g measure pins voltages on the pin header) which could be done or any way to troubleshoot the issue.

Thanks

I purchase an UP board as a part of the Robotics Development Kit (SKU:953143) from Intel Click store (Order# CLK00226215) on 08/15/2017. I only had only one opportunity to power on the board, and it has been sitting in my hobby box ever since. I did not install the operating system to date. Finally, I got over the inertia and tried to install Ubilinux. When I powered the board, I could not see anything on the HDMI screen. The fan and blue LED seem to turn on.

Has my board gone bad? I am surprised that the board can go bad even without doing anything. My Raspberry Pi and Beaglebone have gone through a similar treatment, but they seem to work just fine. Is there a way to revive the board, or is fit for a paperweight now?

I noticed that this board has a BIOS/CMOS battery unlike my Pi/Bealgebone - is there a likely hood that the board will not boot if the battery is dead? I thought a dead battery should atleast show me the UP splash screen on boot until POST.

I know its late, but is there a way I can request an RMA from AAEON(ASUS) or INTEL? Since I bought this from Intel Click store, I am totally confused about what to do! Feels like 230$ down the drain

Any help, inputs or suggestions to revive the board will be helpful.

Best regards,
Sam V

I got the UP board and the official power 5V supply yesterday but cannot get anything to display via HDMI. I've tried a number of the solutions here without any effect.

• It's a new UP board, came with the accompanying power supply

• I I've plugged into a number of different displays. It displayed once (showed first step of Ubuntu 16 installation step.
  *I have tried 4 different displays and switched cables as well. No luck so far

• I have also attempted the steps mentioned here (disconnecting the CMOS battery) : https://wiki.up-community.org/Not-Booting_or_Powering-Up

• I have tried the settings above with and without the boot USB connected
• I have also tried to boot without the HDMI cable connected for the first few seconds

I am not sure what I am doing wrong. The system powers up, keyboard Caps light toggles, boot USB shows some activity (via its own light), Blue LED light on board is on as well.

I'd be happy to try any recommended troubleshooting steps if anyone knows a working solution.

Thanks for any advice you can offer.

I have recently order 2 boards UP-CHT01-A12-0432 from Mouser.
But when I try to use both of hem they didn't start at all (nothing on the screen except notice "No signal ") and the blue light of the board is glowing and the fan is running.
Both power supply and the monitor(with same HDMI cable) working fine with nVidia Jetson Nano development kit.

I have used recommender adapter (5V/4A).

From Mouser support I have receive statement that the technical support is provided by UP community.

Please advise me what I should do because I really need these boards running.

As the manufacturer told Mouser that I have to ask for a solution here in order to proceed with the warranty case, I'm now doing this.

I have a UP^2 board which worked smoothly for several weeks. Then suddenly it stopped working. When I turn on the power supply, the UP^2 board takes only 0.1A and there is no Video output. I already removed the battery over a weekend (with detached power supply of course) and reinserted it to reset the BIOS, but without any success.

Do you have any idea, how I can further troubleshoot?

The board is mounted in the aluminum case (EP-CHUPSMTVAUPS).

My board's part number is
UPS-APLP4-A10-08128
I purchased from Mouser on 05/29/18

How can I solve this problem?
How can I initiate a RMA request?

Thanks a lot!
Pasquale

I'm using the UP2 power supply and checked it to ensure that it is supplying power.

My board's part number is
UPS-APLP4-A10-0432

I purchased from Mouser on 11/22/18

Currently trying to install Ubilinux 3.0 on an UP that is about 2 months old and when the installer is trying to install files to the EMMC it can't find the drive. Ubilinux 4.0 installs fine.

BIOS Name: [UPC1DM11]

any suggestions?
thanks
-y

Afterwards when trying it with the more reasonable 5V, it did boot to OS, but there was a wisp of smoke coming from somewhere on the board...

I'm wondering how screwed am I? Any guesses for what I managed to fry?

Is there any indicators on the broad shows that it has been powered or I have used a wrong method to power the board?

Or if the board is abnormal, is there any ways to request an rma?

I have update the bios with the latest version but the problem continue to exist.

Any idea how to fix it?

I am not able to wake on lan my up2.
I have no problem with 2 up board, I am able to wake them both, however I am failing to wake up up2.
Do you have any clue what could be issue?
I have reset the board to factory default already, so far no luck.

I am trying to hook the up board into a Picade arcade cabinet. It comes with a 1024x768 LCD panel and a HDMI-to-LVDS board, meaning that the display is driven by HDMI.

In order to set up the board, I plugged it on my desktop 1080p HDMI display and everything was going as expected. I could see the Up board logo at startup, navigate through the BIOS menus, etc. But after moving the board and plugging it to the cabinet's panel, it was not visible on the network. It is only after restarting it without the panel plugged in that it finally booted normally.

This behavior of the board not booting up only happens if this particular panel is plugged and powered on during the first ~3 seconds of the boot process. My best guess is that the BIOS detects the panel and tries to do something with it, but something goes wrong (maybe because of the resolution?) and it remains stuck there. But if the panel becomes visible when Linux starts, it has no problem picking it up.

I have updated the firmware to UPC1DM11, but that did not improve things. I am also thinking of wiring a serial connection to see if I can get more information about what is going wrong from the BIOS.

Potential workarounds that I am considering:

• Adding a time-delay circuit that waits ~3 seconds after power is applied to power the panel,
• Replacing the HDMI-to-LVDS board with another one, maybe eDP-to-LVDS?

But of course, it would be nice to get things working as they should. Would anyone have ideas of how I could debug/fix this issue?

Is this a faulty board, or am I doing something wrong?

Thanks,
Mat