Thanks

[sloppyslobb]

Thanks for all your hard work

[arris69]

hey, nice

[oga83]

That sounds great !
If you can interrupt boot on your unit with Ctrl-C, that means that your serial console is not filtered and restricted to hex digits as it is on BD-E8300.
On BD-E8300, boot cannot be interrupted (or am I missing something ?)

[greenhorn]

Great!

[oga83]

I had a look at /2628.9_189/stblinux-2.6.28/drivers/char/n_tty.c in the BD-E5700 sources : it seems that the debug console is not filtered at all
So, maybe the lucky owners of this unit can also have access to a shell with TDM with something like :

Code: Select all

20102011
20089999
====================================
      [ TOP Debug Menu]
------------------------------------
  1  : SubSystem Print On/Off
  2  : Platform Print Setting
  3  : TD Print Setting
  4  : Performance Print Setting
  5  : Sdal Print Setting
  6  : Sdal Trace Setting
  10 : Factory Debug
  11 : TD Debug
  12 : SubSystem DBG
  13 : SubSystem Info Print
  14 : Optical SubSystem   DBG
  21 : Louvre Print Setting
------------------------------------
  70 : Jade Debug
  80 : PVR Debug
====================================
  99 : Exit
====================================
DBG> : 2
Input Start Level << : 0
Input End Level << : 0

====================================
     [Platform Debug List]
------------------------------------
  1. Basic Platform
  2. Advanced Platform
  3. Java
  4. Pharos
  5. Met Platform
  6. Shadow
------------------------------------
  99 : Exit
====================================
cmd> 2

====================================
     [Platform Debug List]
------------------------------------
  1 : InfoLink Debug
  2 : DeviceManager Debug
  3 : NetworkManager Debug
  4 : FrontRunner Debug
  5 : ContentsManager Debug
  6 : Uniplayer Debug
  7 : NetworkSetup Debug
  8 : PVR Debug
  9 : MediaPlay Debug
  10 : CEC Debug
  11 : PSA Debug
  12 : USBApp Debug
  13 : FlashApps Debug
  14 : SWU Debug
  15 : Map Debug
  16 : Browser Debug
  17 : SEF Debug
  18 : HasApi Debug
  19 : DeviceAPI Debug
------------------------------------
  99 : Exit
====================================
cmd> 2

====================================
     [DeviceManager Debug Module]
------------------------------------
  1 : [OFF] DevMgr        2 : [OFF] DevMgr_FLASH          3 : [OFF] DevMgr_HDD
  4 : [OFF] DevMgr_MSC    5 : [OFF] DevMgr_PTP    6 : [OFF] DevMgr_SS
====================================
 Debug Level = Fatal
====================================
 80 : All OFF
 81 : All ON
 85 : Set Debug Level
====================================
 90 : DeviceManager MW Debug
 91 : DeviceManager SS Debug
 92 : DEV Print Setting
 99 : Exit
====================================
cmd> 90

        ====================================
              [ Device Manager - TOP Debug Menu]
        ------------------------------------
           01  : Start DeviceManager
           02  : Stop DeviceManager
           03  : Suspend Mode Test - Sleep
           04  : Suspend Mode Test - WakeUp
           05  : Start Monitoring
           06  : Stop Monitoring
           07  : Start Stress Test
           08  : Stop Stress Test
        ------------------------------------
           11  : USB Test
           12  : DLNA, FLASH, ODD, HDD, MoIP Test
        ====================================
           21  : Print ALL Device Info
           22  : Print Device Info with KEY
           23  : Print ALL Partition Info
        ====================================
           80  : Print Deadlock Status
           88  : Shell
        ====================================
           FF : Exit
        ====================================
        DBG> : 0x88

VDLinux#>
VDLinux#>

[juusso]

do we have such binary in rootfs?

Code: Select all

/sbin/utelnetd

[oga83]

@juuso:
at least, utelnetd is in the BD-E5700 sources :

Code: Select all

./2628.9_189/uclinux-rootfs/user/utelnetd
./2628.9_189/uclinux-rootfs/user/utelnetd/CHANGELOG
./2628.9_189/uclinux-rootfs/user/utelnetd/README
./2628.9_189/uclinux-rootfs/user/utelnetd/LICENSE
./2628.9_189/uclinux-rootfs/user/utelnetd/Makefile
./2628.9_189/uclinux-rootfs/user/utelnetd/utelnetd.c

It seems that this unit is wide opened compared to others...

[EDIT]I 'm surprised by the exlink signals that are placed on the same pattern than in the BD-D6900. In others BD-E units, they tried to hide them a little more...

[juusso]

Tried to look in to rootfs and figured out we don`t have the firmware decryption key for B-BRCME57BSP...
Anyway, if this HowTo could be confirmed by anyone else... Some new approach to root samsung, but yes, as oga said already, as rule, serial console input is filtered and don`t allow to send ctrl+c, just with rare exclusions (like T-MSV4DEUC) and seems, B-BRCME*.

[sbav1]

[EDIT]I 'm surprised by the exlink signals that are placed on the same pattern than in the BD-D6900.

Hmm, same connector pattern is also present on BD-D5100 mainboard.

It's a shame Broadcom shut down its Blu-ray chip business.. I wonder what chips we can expect in Samsung 2013+ "affordable" Blu-Ray player models: Novatek? Mstar/Mediatek?

[oga83]

Hmm, same connector pattern is also present on BD-D5100 mainboard

Yes, BD-D, not latest BD-E models (like BD-E6X00, BD-E8X00) where the signals are not so easy to find