Now image which is the STB?
Mine HDMU Enigma2.
Ako neko ima stari HDMU molim da ga uplouda negdje da se može skinuti.
Instalirao sam sad HDMU ali ne želi se bootati:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,6)
Edit:
Ugasio sam stb pa ga upalio i sad me stalno baca na:
Hit any key to stop autoboot:
TV HDMI setup ok? HDMI cable ok? FFTeam image working HDMI, read other forums.
Remote control does not work?
If Albis, you must replace the file in the etc directory lircd.conf in FTP.
The image T-com remote is set!
Restart, and we have been working on the remote and web interface, you can set the HDMI.
Info o FFTeam imageu:
-uspio sam nekim scart/svideo kablom dobiti sliku na tvu
slika je loša i nikakva podešavanja ju nisu poboljšala
-daljinski radi ok osim jedne stvari
daljinski ne pali stb
-uspio sam podesiti wifi stick i spaja se na mrežu bez problema
getawey postavke se vračaju na 192.168.1.1....moje su drugačije
-uspio sam mountati mrežni disk (cifs) ali nikako da ga stb vidi
- stb mi ne može naći dlna server
-hdmi...ako u postavkama uključim hdmi cec TV prepozna stb kao duckbox ali slike i dalje nema
Ima tu još puno posla.
Enigma2 je sigurno bolje rješenje ali ja i dalje ne mogu niti jednu instalirati.
Ljudi mene zanima dali je atlantu moguće datjerati da fura kodi (xbmc). Imam jednu viška pa bih ju volio za to iskoristiti ako je moguće.
Ako je moguće može li mi netko linkati guide ili nešto gdje je opisano što se treba raditi.
Kopao sam po ovoj temi ali pola toga ne kužim.
Ljudi mene zanima dali je atlantu moguće datjerati da fura kodi (xbmc). Imam jednu viška pa bih ju volio za to iskoristiti ako je moguće.
Ako je moguće može li mi netko linkati guide ili nešto gdje je opisano što se treba raditi.
Kopao sam po ovoj temi ali pola toga ne kužim.
To nije nikakva tajna, Albis na svojim stranicama piše da je softver baziran na STLinuxu. Isto kao i bilo koji drugi softver za SH4 procesore.
Da, podržava miniPCI, ali ne znam kako bi lemljenje 128 nožica završilo bez pravilne opreme... Linux kao svaki drugi, podržava sve za što mu daš driver.
Doniram 3 STB-a u "znanstvene svrhe"! Mislio sam se zafrkavati sa firmware-om na njima, ali nedostatak vremena je učinio to da samo skupljaju prašinu u radnoj sobi. Dakle STB-i su sljedeći:
Scientific Atlanta IPP330HD - T-Com (star cca 7 godina), adapter i daljinac
Siemens STB-7710 - T-Com (star cca 5 godina), adapter (daljinac izgubljen)
Albis SceneGate 8000 - Optima (star 2.5 godine), adapter i daljinac
Poklanjam ih iz razloga što sam u međuvremenu dobio od Optime onaj mali SML STB i kupio smart TV tako da nemam potrebe za dodatnim media playerom.
Bilo bi odlično kad bi se javio netko iz Vinkovaca ili okolice da se dogovorimo oko preuzimanja jer ova 3 čuda (s opremom) imaju podosta kila a želim izbjeći sve nepotrebne troškove poštarine i sl.
Hi!
I'm trying to estick-JTAG and openocd, but does not want to succeed.
Someone had used such a thing?
Difficult to adjust, should openocd.cfg, sti7105.cfg or pdk7105.cfg, memory.cfg, but I can not find anything.
I got so far:
openocd-code # sudo openocd
Open On-Chip Debugger 0.9.0-dev-00346-g3e1dfdc (2015-03-23-22:07)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Warn : Adapter driver 'opendous' did not declare which transports it allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
Warn : Interface already configured, ignoring
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
RCLK - adaptive
adapter speed: 12000 kHz
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
adapter_nsrst_delay: 1200
jtag_ntrst_delay: 1200
Warn : No opendous_type specified, using default 'opendous'
Info : opendous JTAG Interface ready
Info : This adapter doesn't support configurable speed
Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!!
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: IR capture error at bit 0, saw 0x00 not 0x...3
Warn : Bypassing JTAG setup events due to errors
Warn : gdb services need one or more targets defined
If enabled mb680.cfg in openocd.cfg:
openocd-code # sudo openocd
Open On-Chip Debugger 0.9.0-dev-00346-g3e1dfdc (2015-03-23-22:07)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Warn : Adapter driver 'opendous' did not declare which transports it allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
RCLK - adaptive
adapter speed: 12000 kHz
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
adapter_nsrst_delay: 1200
jtag_ntrst_delay: 1200
/usr/local/share/openocd/scripts//board/mb680.cfg:9: Error: invalid command name "sh4_set_pmb"
in procedure 'script'
at file "embedded:startup.tcl", line 58
at file "openocd.cfg", line 28
at file "/usr/local/share/openocd/scripts//board/mb680.cfg", line 9
Warn : No opendous_type specified, using default 'opendous'
Info : opendous JTAG Interface ready
Info : This adapter doesn't support configurable speed
Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!!
Info : JTAG tap: auto0.tap tap/device found: 0xffffffe1 (mfg: 0x7f0, part: 0xffff, ver: 0xf)
Warn : AUTO auto0.tap - use "jtag newtap auto0 tap -irlen 2 -expected-id 0xffffffe1"
Error: auto0.tap: IR capture error; saw 0x0003 not 0x0001
Warn : Bypassing JTAG setup events due to errors
Warn : gdb services need one or more targets defined
Some are already, seeing the device, no IR capture error:
Info : opendous JTAG Interface ready
Info : This adapter doesn't support configurable speed
Info : JTAG tap: auto0.tap tap/device found: 0xffffffe1 (mfg: 0x7f0, part: 0xffff, ver: 0xf)
Warn : gdb services need one or more targets defined
The Albis JTAG connection is good?:
TDI -- 13
TMS -- 9
TRST -- 19
SRST -- 17
TCK -- 11
TDO -- 15
GND -- 20
You need a few more wires. Take a look here:
And it's the best if you do it with FT2232/FT4232.
Jtag pinout is ok.No need more connection but Openocd not work with sh4/st40, must use STMCLT1000 "ST micro connect light" and STLinux jtag debug software.
USB_JTAG ftdi mini modules : 1.ft232 2.ft2232 3.ft4232.
Or if you can change of your estick-jtag vid and pid to STMCLT vid 0x0483 pid 0x3747 maybe can use with STLinux software.
Hi!
HxD Hexeditor works.
Estick usbview list:
idVendor: 0x1781
idProduct: 0xC0C0
ConnectionStatus: DeviceConnected
After replacement, estick driver not work, needed st driver, I try to:
idVendor: 0x0483 (STMicroelectronics)
idProduct: 0x3747
ConnectionStatus: DeviceConnected
Zorin Lite:~$ lsusb
Bus 004 Device 002: ID 0483:3747 STMicroelectronics ST Micro Connect Lite
zorin lite# :/opt/STM/STLinux-2.4/host/bin# sh4-linux-gdb
GNU gdb (GDB) STMicroelectronics/Linux Base 7.6-76 [build Jul 2 2014]
Copyright (C) 2013 Free Software Foundation, Inc.
(gdb) sh4tp STMCLT1000_A:pdk7105:ST40,se=1
The target is assumed to be little endian
SDI [ERROR] :: [SERVER] host_JTAG_DeviceID: Unknown device identifier STMCLT1000_A
SDI [ERROR] :: [SERVER] processSDICommand: sdi_Initialise failed
SDI [ERROR] :: Command SDI_INITIALISE failed (0)
SHDEBUG [ERROR] :: Unable to initialise SDI interface
Unable to connect to remote target STMCLT1000_A:pdk7105:ST40,se=1
(gdb)
Stlinux is installed on Fedora 20 and Zorin Lite 9.
Still need to improve something, maybe a name or STMCLite serial number?:
Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0483 (STMicroelectronics)
idProduct: 0x3747
bcdDevice: 0x0001
iManufacturer: 0x01
0x0409: "www.technikum-wien.at"
iProduct: 0x02
0x0409: "estick-jtag"
iSerialNumber: 0x03
0x0409: "000000000000"
bNumConfigurations: 0x01
ConnectionStatus: DeviceConnected
Thank you!
This is lsusb of STMCLT clone but i think you can't use your usb-jtag because must be ftdi chip on it.
Device: ID 0483:3747 SGS Thomson Microelectronics
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0483 SGS Thomson Microelectronics
idProduct 0x3747
bcdDevice 8.00
iManufacturer 1 ST
iProduct 2 ST Micro Connect Lite
iSerial 3 STMCLT1030
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 101
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 ST Micro Connect Lite
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 ST Micro Connect Lite
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 ST Micro Connect Lite
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 ST Micro Connect Lite
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08 EP 8 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
znam da je tema starija ali imam pitanje u vezi max tv recivera.imam pace reciver(dvb-t ne iptv)ali iza ima usb i ethernet port pa da vidim jel iko zna sta bi s njim mogao da radim?
Kroz mrezu i usb vjerovatno nista ali probaj ga otvorit i detaljnije slikat plocu(mbo) pa mi posalji slike onda bi ti mogao mozda pomoci oko njega.
Trebalo bi vidi koji procesor koristi dali ima ttl(rs232) pinove na ploci, jtag ili nesto s cim bi se mogala dumpat memorija i eventualno ubacit nekakav drugi bootloader ili software.
Hi!
Interestingly dmesg.
FTDI 's see the Atmel chip and also charges the FTDI driver and serial port, JTAG.
dmesg: usb 5-2: new full-speed USB device number 2 using uhci_hcd
[ 84.843055] usb 5-2: New USB device found, idVendor=0483, idProduct=3747
[ 84.843059] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 84.843062] usb 5-2: Product: estick-jtag
[ 84.843064] usb 5-2: Manufacturer: www.technikum-wien.at
[ 84.843066] usb 5-2: SerialNumber: 000000000000
[ 84.872954] usbcore: registered new interface driver usbserial
[ 84.873239] usbcore: registered new interface driver usbserial_generic
[ 84.873497] usbserial: USB Serial support registered for generic
[ 84.897071] usbcore: registered new interface driver ftdi_sio
[ 84.898218] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 84.899450] usb 5-2: Ignoring serial port reserved for JTAG
lsusb: Bus 005 Device 003: ID 0483:3747 STMicroelectronics ST Micro Connect Lite
Nije mi jasno kako nisam prije vidio ovu temu :/
nego kako radim u štekomu imam pristup stb-ovima.
samo prije nego zapocnem ista moram se uhvatit i procitat ovih 41 stranicu ili ako ima neko da kaze dali se uspijelo sta napravit ili ne.
Ništa pametno se nije uspjelo. Trebao bi nam stock FW za STB-7710 (Albis/Siemens)...
Hi!
I got a such a thing, you can do something about it, yet I can not reprogram the FT_prog, which firmware should be added?
http://vonkonow.com/wordpress/2011/12/using-a-sony-ericsson-dock-as-an-usb2serial-adapter/
Blagus could be programmed through.
The eSticK also rebuild Flashcatusb, working, but the connection is still not good.
Hi!
I got a such a thing, you can do something about it, yet I can not reprogram the FT_prog, which firmware should be added?
http://vonkonow.com/wordpress/2011/12/using-a-sony-ericsson-dock-as-an-usb2serial-adapter/
Blagus could be programmed through.
The eSticK also rebuild Flashcatusb, working, but the connection is still not good.
You can't use that SE dock as JTAG adapter. Only UART. You have to add VID/PID of the dock into FTDI driver inf files and you'll get a COM port on the PC.
And you can't use Flashcatusb. FT4232 costs only €20 and it will work.
Never mind, there are two good Albis 8000.
There is another new image?
Počeo sam pisati tutorial o upogonjavanju čistog STLinuxa na našem STB-u (Albis STB-8000), ali i ST-baziranim STB-ovima općenito. Koga zanima, može početi čitati ovdje: http://blagus.info/stlinux-env-setup-part1/
Pišem kako uhvatim vremena.
Još samo da komentiram ono što sam pročitao gore: ne postoji "stock" FW za Albise, ali to vrijedi i općenito za sve ISP-dedicated STB-ove. Postoje samo varijante sučelja (Ekioh, Java, Flux,...) i opcionalni dodaci (što piše u datasheetu), a na ISP-u je da konfigurira middleware i customizira sve za svoje potrebe.
Dakle, nema "stock" FW-a jer se FW radi po narudžbi ISP-a. Jedino da potrefimo nekog s dobrim middlewareom i sučeljem. Imam jednog takvog, ali zaključan mu je i JTAG i SSH i serial, tako da ga mogu samo gledati (za sad).
Hi!
It is based on 8000 Albis be paid to image:
http://www.opena.tv/howtos/8187-build-own-openatv-sh4-image.html
sti 7162 Models:
amikoalien, sognotriple, sparktriplex, sabtriple,giavatar, sparkone
Which is good from 7162?
Currently turn sparkone.
It works Albis 8000?
#Raxone
Kodi no prescription or 4.5 Hyperion image.
How to translate Albis 8000?
Other:
Thank you!
