Talk:Main Page
From Sharpfin
The main discussion page is used for generic discussions about the project. Add your comments below, and make sure to end it with ~~~~ to timestamp your contribution.
Contents |
[edit] Bla
Hi. I think it's a good idea to profile the project as an attempt to understand the hardware only, and state explicitly that we are *not* interested in reverse engineering the Reciva software or their database. Digging too deep into the Reciva software might cause problems because that's the only truly proprietary part of the device. Agree ? Ico 19:17, 29 October 2006 (CET)
[edit] Google gives some information
A Google search on reciva helix shows some interchanges between John Stirling of Reciva and the Helix community etc, which casts some light on how they have adapted the open source for their purposes. I agree with you about not digging too deep into the proprietary part of the device, but I think these exchanges are about how they are adapting the Open Souce code they are using, which should be OK? --Cornwell 16:41, 28 December 2006 (CET)
This must be ok - they used GPL licensed software, which gives us the right to use and modify it for our own purposes. I expect there would be one closed-source app running in the box, which is the actual radio application handling the user interface and the communication with the Reciva database. Better not fiddle with that. Ico 21:42, 29 December 2006 (CET)
[edit] Finally! Shell access...
Okay, this may be of some use to Sharpfin. I understand that the project aims are to understand the hardware rather than reverse engineering the software. As are mine. However, being able to get inside a working box and use the existing infrastructure (bootloader, familar linux installation etc) is likely to be a useful starting point for creating and testing new software.
I've managed to install dropbear on a Logik IR100 - giving SSH access to the box. The hack itself wasn't easy and has taken a few weeks and many dead ends. Having got the hard work out of the way it is fairly easy to apply to other radios. Details to follow here: Internet Radio Exploration. There are only a few photos at the moment but I'm going to flesh out the details as soon as I get chance. Only software is required to get shell access (a DNS server and web server) but I had to have a poke around the flash chip to work out how to do it. Rdk 14:41, 5 April 2007 (CEST)
[edit] Bricking
A warning to anyone else who might make the same mistake. I was looking through the kernel source, and came across some special unicode characters that are supposed to translate to icons. I tried them out by saving them as the greeting message in the config file (UTF-8 encoded) - if you've got shell access and have had a poke around, you probably know the file I mean. Now the radio fails to boot properly. --Jpr 18:55, 3 August 2007 (CEST)
Did you manage to fix this again ? Ico 08:58, 24 August 2007 (CEST)
Not yet, it looks like I'll need to call on a friend with JTAG experience. I was hoping someone might find the serial port in the meantime, as I'm sure the kernel is booting (there are flashing LEDs inside), it is just the reciva app that is failing to start (hopefully before initialising the watchdog). Something similar to the procedure for getting SSH onto the radio with JTAG should work though. --Jpr 15:23, 24 August 2007 (CEST)
- I eventually managed to fix it, after destroying my parallel port trying to JTAG it and giving up, by getting hold of a MagicBox Imp and swapping the Barracuda modules. The Imp module didn't work in the Logik (screen filled with blocks), but I was able to boot the Imp with the Logik's module in it and re-edit the config1012.txt file. It turns out I'd also managed to accidentally convert it to DOS line ends when I'd saved it as UTF-8, so I'm not sure whether the problem was caused by that, or the UTF-8 character. --Jpr 11:32, 28 May 2008 (CEST)
The serial port will probably not be of any help, since nothing is listening to it on the radio. I think you should put your hope to the JTAG solution. The manufacturer of the CPU provides a simple piece of software to drive a resistor-network JTAG port, so you might be able to get things to work with that. I'm planning on giving that a try myself one of these days, since it would be reassuring to know there is a way to restore things when I mess up. Good luck, let us know your results! Ico 20:22, 24 August 2007 (CEST)
Made mistakes:
Hi, i edited the config1012.txt. I added four or five entries and now the radio only displays "Reciva Radio ARM powerded".
Do I need the IC 74AC244 for unbricking it with a JTAG cable? Does it also works with a IC called "74HC244" ?
An other question is : How to compile the software sharpflash. I use ubuntu 7.10 but "make" or "make -f Makefile.windows" creates several error:e.g. "ppt.c:1:19:error:stdio.h: No such file or directory"
It's true. Sharpflash-src-0.1.tar.bz2 doesn't contain stdio.h
EDIT
I forgot to install "libc6-dev"
Ubuntu 7.10-> sudo apt-get install libc6-dev
Maybe someone can help me (; regards tim(max)--Tim 01:26, 10 January 2008 (CET)
Hi, could i also use the "unbuffered cable" ?
->http://wiki.openwrt.org/OpenWrtDocs/Customizing/Hardware/JTAG_Cableb
trumpton: - i'd recommend NOT using an unbuffered cable. The processor on the barracuda module is running at 1.8V core, nd 3.3V I/O - it is almost a certainty that your PC printer port is 5V - whilst the series resistors in the unbuffered cable may stop the processor being overstressed, it needs some maths to work it all out. It is far safer to use the buffers, which are powered from the barracuda module itself.
EDIT
I tried a 74HC244 and the programmer works.--Tim 20:06, 15 January 2008 (CET)
[edit] Fix a frozen IR100
Hello,
does anyone fixed the bluescreen problem?
I have replaced all capacitors on the mainboard, but still it doesn't work...
A green LED is flashing but you cannot operate the radio and it only displays these blocks ):
--Tim 22:37, 26 December 2007 (CET)
- I resoldered the cristal on the reciva-module. Now it's working--Tim 01:09, 10 January 2008 (CET)
- Might have to try that. I have a module here from a Magicbox Imp, which doesn't get past the "Reciva Powered" at boot, but when I put the module into my Logik, it has this bluescreen problem, so perhaps different radios exhibit different behaviour for the same hardware fault. -- Jpr 11:31, 28 May 2008 (CEST)
I have a unit with the same problem, I've re-soldered the crystal but it didn't change the blocks on the screen :( any other ideas? -- Phily 00:00, 28 June 2009 (CEST)
[edit] Did anyone figure out the connectors for S/PDIF out?
Reciva's specs of the Baracuda module include "mono or stereo digital out" - does anyone have a radio where this is actually implemented or figured which connector carries the signals?
Jaw 16:19, 6 March 2008 (CET)
The Reciva board based on a samsung s3c2410 chip. Maybe you can figure out it with the help of that datasheet.
--Tim 17:43, 6 March 2008 (CET)
[edit] Roberts WM201
Just got a Roberts WM201. Has anyone installed the web/telnet hack on one of these?
Once the web interface is installed is it possible to control the radio via the web? I think this would be a good thing as browsing all my MP3s via the radio dial is pretty clunky!
Dicko 14:20, 13 March 2008 (CET)
[edit] update an IR100 with firmware v257-a-615-a-075
Hello,
Yesterday I tried to update my radio but the patchfile only has had an size of 55Byte. Today, I tried it again but now the server isnt't available. Does anyone else updated successfully an IR100 with the v257-a-615-a-075?
trumpton - interesting. What you have downloaded is a compressed text file, which contains the words: "Status: 404". It looks like the 615 firmware is no longer where we expect it to be. Other versions appear to be OK.
max: mmh, how installed m0aur and Rfcvb72 the 615 firmware ? ->http://sharpfin.zevv.nl/index.php/Sharpfin_Matrix
trumpton: I suspect something has changed at the Reciva end. 404 = Not found - this error message is put in a text file, then compressed (by Reciva).
dgp1000. I also did the same on a Tevion and could not find it. But there is a new file 257-a-615-a-076 which I have not tried yet. Has anyone else???
trumpton: How did you find this file - did you guess the name?
dgp1000 Yes. When 075 seemed to have gone missing, I just added 1 to get 076. But this is my first Reciva radio and I only bought it yesterday, so I am not an expert in any sense of the word.
trumpton Absolutely inspired!!! I've put the -76 on both an IR100, and a Tevio 5404, and they both work OK.
[edit] Downgrading firmware
Hi, I've successfully installed the Sharpfin base patch and various firmware versions on my IMP Magicbox. Most of the newer versions worked really well, but at least since I'm on the 257-a-756 series firmware I can't downgrade.
I tried both, to provide a patchfile manually using the patch server and just to automatically "update" directly from the Reciva server (officially, the IMP is still on v257-a-181 from May 2007!). Neither approach worked. On providing a manual downgrade, the radio runs through the installation procedure and reboots, but afterward all is the same. On the auto-update, it just says that no update is available.
I tried various version of the firmware to get around the 802.11n problem, but eventually had to replace the wlan module to get it back working. So now I'm on firmware v257-a-756-a-199, which performs poorly on the radio.
In the beginning it worked ok for most radio functions, but now it seems to be unable to load the station list from reciva or reconnect to favourite stations already stored on the radio. Only podcasts and on-demand content seems to work. Could it be that the radio is running out of memory? Or is the reciva gateway refusing to work with radios having the wrong firmware version?
I don't want to update any further, but at the same time that seems to be the only way open to me right now. Any thoughts?
--Imp de 18:58, 8 November 2008 (CET)
[edit] Revo Blik Wifi: sharpfin-test.patch not working
I just acquired a Reve Blik Wifi with V1.2.4.14625-1B4 sw version. When trying the test-patch (in Linux) it is not intercepting the Software Update check. The Revo Blik Wifi has IP address 192.168.1.16.
Any ideas on this problem?
Here is a capture of the server messages:
Please enter the name of the patchfile (e.g. c: est.tar.bz2): ./sharpfin-test.patch Please enter the IP address of your real DNS server: 192.168.1.1
Setting nameserver to: 192.168.1.1 Patch file is ./sharpfin-test.patch
patchserver: Running webserver on port 80 patchserver: running DNS Server on port 53 webserver: waiting for connections ... dnssever: waiting for connections ... dnsserver: 192.168.1.16: lookup pri.logon.wifiradiofrontier.com ... OK dnsserver: 192.168.1.16: lookup time.wifiradiofrontier.com ... OK dnsserver: 192.168.1.16: lookup time.wifiradiofrontier.com ... OK dnsserver: 192.168.1.16: lookup time.wifiradiofrontier.com ... OK dnsserver: 192.168.1.16: lookup pri.logon.wifiradiofrontier.com ... OK dnsserver: 192.168.1.16: lookup pri.wifiradiofrontier.com ... OK dnsserver: 192.168.1.16: lookup stream.crossmediaventures.com ... OK dnsserver: 192.168.1.16: lookup update.wifiradiofrontier.com ... OK
Thanks, Bassie 14:46, 24 January 2009 (CET)
The answer is pretty obvious: This is not a reciva radio!
Karlkloss 17:59, 29 March 2009 (CET)
