Odroid N2 test builds

Ray · 18 April 2019 19:10

Question is can you still ssh into the box after suspend?

Gobol · 18 April 2019 19:35

Got few of usb-uarts around.

CH340 works. @ shutdown :

wake-on-lan = 00000001
bl30 get wakeup sources!
process command 00000006
bl30 enter suspend!
Little core clk suspend rate 1896000000
Big core clk suspend rate 24000000
store restore gp0 pll
suspend_counter: 1
Enter ddr suspend
ddr suspend time: 17us
alarm=0S
process command 00000001
cec ver:2018/04/19
CEC cfg:0x003f
WAKEUP GPIO cfg:0x00000000
use vddee new table!
08915d0000000000cec reset
Set cec pinmux:0x11
kern log_addr:0x0f
cec T: 11
cec_triggle_tx:TX_ERROR
Set cec log_addr:0x01, ADDR0:11
WAKEUP GPIO FAIL - invalid key
fffffe71
customer pwrkeys for IR is NULL, use defaults!

customer pwrkeys for IR is NULL, use defaults! - looks like IR did not get proper key…

supersnail · 18 April 2019 19:38

Some experimenting with different SD cards.

All tests used April 14th N2 image clean. I did do a library import
each time to have movie library to scroll thru for testing disk access.

Transcend cards seem to work just fine

The Sony SD does the removal notification and yanks the file system
upon resuming from suspend.
sony64.txt (97.6 KB)

All of the Sandisk cards I have behave same exact way. When
resuming from suspend subsequent access is very slow and kernel log filled
with SD messages. Note it’s possible to suspend without this problem occurring. Usually found you have to be in movie library to trigger it. Sometimes it takes a few tries to reproduce.
sandisk200.txt (3.4 MB)

Ran into unrelated CEC problems resuming.

Have a Sony 690e TV. In CEC configuration within Kodi if Devices to power on and power off are
set ‘TV’ the TV flakes out about a third of the time and when turned back on won’t unsuspend
Kodi. In this case if I pull the power cord on the TV then turn it on the N2 resumes so seems to be a TV problem.

With setting of ‘None’ rather than ‘TV’ behavior is consistent and resume always works reliably. Kodi
should probably suppress echoing power messages to the same thing that requested Kodi power up/down in the first place assuming this is what’s happening.

rosenrot · 18 April 2019 20:29

Watching livetv I get following errors:

https://justpaste.it/2pnwz

If you need further information, please tell me what is required. I’m happy to help.

Another one: https://justpaste.it/5jqr0

This one freezes the entire box, I have to re-plug the power cord.

Update: 4k movies or livetv result in an image which spans over 1/4 of the screen. Resolution stays at 1080p. Whitelist untouched after fresh install.

Ray · 18 April 2019 20:50

Thanks for all the testing I could not reproduce with my 16G sandisk. But your logs might help figuring this issue out.

Ray · 18 April 2019 20:52

It does indeed look like it didn’t work. Can you try suspend too?

albanibr · 18 April 2019 21:28

I’m using a 16gb sandisk SD and it works great, even when it suspend.

but the memory usage is high. I’m using the same addons I used in C2 and it was only 500mb

farhanito · 19 April 2019 00:34

Modifying setenv remotewakeup in boot.ini works for me.
What should I put in config.ini?

Ray · 19 April 2019 04:50

github.com

CoreELEC/CoreELEC/blob/coreelec-9.0/projects/Amlogic-ng/bootloader/config.ini#L140


#------------------------------------------------------------------------------------------------------
#
# config.ini
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# Console Setup
#
# consoleopt='console=ttyS0,115200 console=tty0 no_console_suspend'
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# CPU Frequency Control
#
# WARNING!!! WARNING!!! WARNING!!!
#   Before changing anything here please read the wiki entry at:
#   https://wiki.odroid.com/odroid-n2/application_note/software/set_cpu_freq
#
# max_freq_a73='1800'
# max_freq_a53='1896'
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# HDMI CEC Control, 0=disable/1=enable
#
# hdmi_cec='1'
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# IR setup for Odroid N2
#   Setup a custom keycode to wake the N2 from suspend or poweroff
#   You can stop kodi and eventlircd and use "ir-keytable -u" to obtain a compatible u-boot
#   IR keycode
#
# remotewakeup='0x31ce4db2'
#
#   decode_type can be one of the following:
#   NEC='0x0', DUOKAN='0x1', TOSHIBA='0x2', RCA='0x3', RC5='0x4', RC6A='0x5', NEC_TOSHIBA_2IN1='0x6',
#   NEC_RCA_2IN1='0x7', RCMM='0x8', NEC_RC5_2IN1='0x9', NEC_RC5_2IN1='0xa', RC6='0xb'
#
# decode_type='0x0' # NEC
#
#   remote power key mask:
#   Some IR protocols implement a toggle bit, this can be ignored by the "and" mask:
#   RC5='0x37ff', RC6='0x1effff', RC6A='0xffff7fff'
#
# remotewakeupmask='0xffffffff'
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# WOL Setting for Odroid N2, 0=off/1=on
#
# wol=1
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# Heartbeat for Odroid N2
#   You can disable the blue LED heartbeat with this option, 0=off/1=on
#
# heartbeat=1
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# EMMC Timeout for Odroid N2
#   BL1 is configured to boot from eMMC before SD-card, this option is useful if you have another OS
#   installed on to an eMMC as it will delay bootup by 30s allowing you to boot from an SD-card and
#   attach the eMMC during this time, u-boot will then boot from the SD-card and the eMMC will be
#   be available to the OS allowing you to use installtoemmc or browse the eMMC contents.
#
# emmc_timeout=1
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# Power Off and Wake Up using GPIO Key Button for Odroid N2
#   Valid options are 476,477,478,479,480,481,483,484,485,486,487,488,489,490,491,492
# 
# gpiopower=476 # (pin 16 of J2 header)
#
#------------------------------------------------------------------------------------------------------

#------------------------------------------------------------------------------------------------------
#
# CoreELEC Developer Options
#   Valid options are: textmode debugging progress nofsck nosplash noram overlay quiet ssh
#
# coreelec='quiet'
#
#------------------------------------------------------------------------------------------------------

These are the examples in config.ini

Ray · 19 April 2019 04:52

You have overscan setup in your guisettings.xml

Ray · 19 April 2019 05:41

Here is a testbuild trying to fix the SD card issue. I didn’t get my Samsung SD card so I could not test yet:
https://test.coreelec.org/ray/CoreELEC-Amlogic-ng.arm-9.0-devel-1555651433.tar

kostaman · 19 April 2019 06:45

Same bad results. No change.

rosenrot · 19 April 2019 08:04

Honestly, I don’t think this is something I could solve with any overscsn settings.
https://send.firefox.com/download/a2af933642f7a8bc/#pC-8K4PHGLfBR9XbD5Izbw

This worked without any problems some builds ago.

Ray · 19 April 2019 09:07

Look into your guisettings.xml

Daaave · 19 April 2019 10:10

The only adjustments I could find in ir-keytable are Delay and Period which are to do with how long a key is pressed down. My problem is that after you press one key you need to wait almost a second before pressing another key or the press isn’t recognised.

Anyway the main problem turns out to be my USB DVB dongle. If I stop TVHeadend the HK remote improves, and if I remove the dongle altogether the remote is just about perfect.

I don’t know if this is fixable or not, but I guess it should be as the IR remote on my S905 box works perfectly while using that dongle.

It’s a PCTV Triplestick 292e.

cdu13a · 19 April 2019 11:05

Unfortunately, the magic special sauce behind how the DVB driver stuff works, breaks stuff and makes it a nightmare to maintain and deal with IR remote stuff. The IR remote when not using the DVB stuff works reasonably well, though I do plan on making a few more improvements to it. Hopefully we can figure a way to lower the burden caused by DVB stuff and make it so there is no problems when using an IR remote with the DVB stuff.

Daaave · 19 April 2019 11:12

Thanks so much for the reply, I understand it must be a bloody nightmare.

I think my wife is finally getting used to the airmouse/kb now anyway after me constantly reminding her “spacebar to pause/play and C for menu”

roidy · 19 April 2019 11:41

@Daaave I can highly recommend the Amazon Alexa remote paired with a super cheap CSR8510 bluetooth dongle, works perfectly and is more responsive than any IR remote.

I’ve tried my OSMC remote as well which also works perfectly fine out of the box.

Daaave · 19 April 2019 11:47

Can these remotes be configured to switch the N2 on? (startup from shutdown state I mean)

Thanks for your help

Gobol · 19 April 2019 11:47

I’ve checked both poweroff / systemctl suspend - no diff.
Last line after kernel up is always:

CoreELEC:~ # pwr_key=1fe0f807

If it means anything… didn’t find reference to such variable anywhere in sources…