Sharpfin - User contributions [en]

Sleep timer

2025-06-08T14:18:27Z

Philipp: Created page with "When I first base patched my LOGIK IR100's there were values in the config files for the sleep timer. After upgrading to the v 257-a-421-a-057 service pack, the original unlimited sleep timer is now limited to three hours, and I can find no reference to it in the config file. Any help to increase the sleep timer would be appreciated."

When I first base patched my LOGIK IR100's there were values in the config files for the sleep timer. After upgrading to the v 257-a-421-a-057 service pack, the original unlimited sleep timer is now limited to three hours, and I can find no reference to it in the config file. Any help to increase the sleep timer would be appreciated.

Config Options List

2025-06-08T13:46:04Z

Philipp:

= Config options for different firmware versions =

Some of these are already documented on: [[Config.txt_File]]

Once you know the purpose and can document usage, please update: [[Config.txt_File]]

FW v257-a-421-a-091 - Feb 2008

FW v257-a-421-a-057 - Jan 2008

Config Options List

2025-06-08T13:45:38Z

Philipp: Created page with "= Config options for different firmware versions = Some of these are already documented on: Config.txt_File Once you know the purpose and can document usage, please update: Config.txt_File FW v257-a-421-a-091 - Feb 2008 FW v257-a-421-a-057 - Jan 2008"

Vistron MX-200i

2025-06-08T13:38:39Z

Philipp: Created page with "Introduction ---- This radio first appeared in 2008 and was sold by eBuyer UK. References ---- http://logikir100.tripod.com/Vistron.htm"

Introduction
----
This radio first appeared in 2008 and was sold by eBuyer UK.

References

----
http://logikir100.tripod.com/Vistron.htm

OpenOCD

2025-06-08T13:31:46Z

Philipp: Created page with "== <big>Barracuda module debug over JTAG using OpenOCD</big> == It was tested on Ubuntu 10.04 LTS and reciva-kernel-v24080215+00.tar.bz2 kernel pack. ===OpenOCD installation and testing === To install openocd in Ubuntu enter command sudo apt-get install openocd Create openocd config file ''JTAGdebug.cfg'' with this contents: # # Parallel port wiggler (many clones available) on port 0xc8b8 # telnet_port 4444 gdb_port 3333 interface parport parport_port 0..."

== <big>Barracuda module debug over JTAG using OpenOCD</big> ==

It was tested on Ubuntu 10.04 LTS and reciva-kernel-v24080215+00.tar.bz2 kernel pack.

===OpenOCD installation and testing ===

To install openocd in Ubuntu enter command

sudo apt-get install openocd

Create openocd config file ''JTAGdebug.cfg'' with this contents:

#
# Parallel port wiggler (many clones available) on port 0xc8b8
#
telnet_port 4444
gdb_port 3333
interface parport
parport_port 0
parport_cable wiggler
# Found on the 'TinCanTools' Hammer board.
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME s3c2410
}
if { [info exists ENDIAN] } {
set _ENDIAN $ENDIAN
} else {
# This config file was defaulting to big endian..
set _ENDIAN little
}
if { [info exists CPUTAPID] } {
set _CPUTAPID $CPUTAPID
} else {
set _CPUTAPID 0xffffffff
}
#use combined on interfaces or targets that cannot set TRST/SRST separately
reset_config trst_and_srst
#jtag scan chain
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID
set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME arm920t -endian $_ENDIAN -chain-position $_TARGETNAME -variant arm920t
$_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x30800000 -work-area-size 0x20000 -work-area-backup 0
# speed up memory downloads
arm7_9 fast_memory_access enable
arm7_9 dcc_downloads enable
nand device s3c2410 s3c2410.cpu

Now it's possible to test OpenOCD.
Connect JTAG cable to pc, power on radio and execute command in a shell

sudo openocd -f JTAGdebug.cfg

You should see the output

Open On-Chip Debugger 0.3.1 (2010-01-18-14:21)
$URL$
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
parport port = 0
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
fast memory access is enabled
dcc downloads are enabled
Error: Translation from jtag_speed to khz not implemented
Info : interface specific clock speed value 0
Info : JTAG tap: s3c2410.cpu tap/device found: 0x0032409d (mfg: 0x04e, part: 0x0324, ver: 0x0)
Warn : JTAG tap: s3c2410.cpu UNEXPECTED: 0x0032409d (mfg: 0x04e, part: 0x0324, ver: 0x0)
Error: JTAG tap: s3c2410.cpu expected 1 of 1: 0xffffffff (mfg: 0x7ff, part: 0xffff, ver: 0xf)
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Info : Embedded ICE version 2

Now you can halt radio connecting to OpenOCD with telnet in a new shell window

telnet localhost 4444

Telnet output :

Code: [Select]
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
>

In telnet terminal enter command ''halt'' and terminal writes

> halt
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x20000093 pc: 0xc0015c74
MMU: enabled, D-Cache: enabled, I-Cache: enabled
>

Now we can power off radio and go to second part.

=== Kernel with debug options compiling ===

To see debugging symbols in gdb shell you need compiled kernel with debug option enabled.
In reciva kernel Makefile you need to add -g option after -Wall in these 2 lines:

HOSTCFLAGS = -Wall '''-g''' -Wstrict-prototypes -O2 -fomit-frame-pointer
CFLAGS := $(CPPFLAGS) -Wall '''-g''' -Wstrict-prototypes -Wno-trigraphs -O2 \

Now you can rebuild kernel.
After build you need a file vmlinux from reciva kernel root dir it's about 32M size.

If your radio kernel version is the same like kernel source you can skip information below how to flash new kernel to radio.

=== New kernel flashing ===

The kernel file zImage could be found in folder
/arch/arm/boot

To be suitable for sharpflash you need to use getpart utility

getpart zImage 0 fc000 kernel.new

After this kernel.new size must be the same like kernel-mtd.bin from backups.

<span style="color:#FF0000"> <big>Before doing this be sure you have backup of your radio working kernel partition.</big>

Now turn on radio and sharpflash the new kernel.

sharpflash -w kernel.new 4000 fc000
When flashing is finished restart radio.
If you have changed in kernel source something, for debugging must use apropriate vmlinux file.

=== Debugging with gdb ===
Turn on radio.
Run OpenOCD and telnet. Enter ''halt'' command in telnet window when radio display lights up.
Now we need to run gdb in a new shell window.

root@reciva-dev:/home/shared# gdb

Gdb output screen

GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb)

to load debug symbols in gdb environment execute ''file vmlinux''.(I have copied vmlinux file to the place where execute gdb in my case /home/shared)

(gdb)file vmlinux

Output:

Reading symbols from /home/shared/gdb/vmlinux...done.
(gdb)

Now connect to OpenOCD enter in gdb this command

target remote localhost:3333

Output :

Remote debugging using localhost:3333
0xc01b8d28 in cr_alignment ()
(gdb)

Now i'ts possible to get kernel variable values.

Below it's shown method how to get dmesg printout using log_buf variable.

===Gdb script for dmesg===

You can simply copy paste this script to gdb environment

define dmesg
set $i=0
set $end_idx=(log_end -1)
while($i< logged_chars)
printf"%c",log_buf[$i]
set $i=$i+1
end
end

At the end you need to press enter.
Output :

(gdb) define dmesg
Type commands for definition of "dmesg".
End with a line saying just "end".
>set $i=0
>set $end_idx=(log_end -1)
>while($i< logged_chars)
>printf"%c",log_buf[$i]
>set $i=$i+1
>end
>end
(gdb)

Now execute ''dmesg'' command in gdb shell

(gdb) dmesg
<4>Linux version 2.4.26-vrs1-bast2 (pb@bob.internal.reciva.com) (gcc version 3.3.4) v24080215+00 #1 Fri Feb 15 17:33:14 GMT 2008
<4>CPU: Arm920Tid(wb) revision 0
<4>Machine: Reciva-IR2
<4>HWCONFIG values are: 15 1f (1013)
<4>S3C2410: 202.800000 MHz, memory 101.400000 MHz, pclk 50.700000 MHz
<4>On node 0 totalpages: 8192
<4>zone(0): 8192 pages.
<4>zone(1): 0 pages.
<4>zone(2): 0 pages.
<4>Kernel command line: root=/dev/mtdblock2 ro init=/linuxrc
<7>Relocating machine vectors to 0xffff0000
<4>irq: clearing subpending status 00000402
<4>bast_init_irq:
<4>setup_timer: TCNTB4 at d890003c
<4>setup_timer: tcon=00000000, tcnt should be f799
<4>setup_timer: about to configure timer4
<4>setup_timer: stopping timer
<4>setup_timer: adding interrupt
<4>setup_timer: starting timer
<4>Calibrating delay loop (skipped)... 101.17 BogoMIPS
<6>Memory: 32MB = 32MB total
---Type <return> to continue, or q <return> to quit---

Pressing enter you can read all dmesg.

MediaWiki:Sidebar

2025-06-08T13:11:14Z

Philipp:

MediaWiki:Sidebar

2025-06-08T13:10:34Z

Philipp:

MediaWiki:Sidebar

2025-06-08T13:10:08Z

Philipp:

MediaWiki:Sidebar

2025-06-08T13:09:48Z

Crosscompiling

2025-06-08T13:05:58Z

Philipp:

== Simple "Hello World" ==

Assuming you have built the [[Toolchain]], made the changes to your environment including PATH and carried out the instructions [[Enabling Login]], a simple "Hello World!" program is easy to build.

For the sake of this example we'll set up an alias to the crosscompiler.

alias cc=arm-9tdmi-linux-gnu-gcc

In a working directory, create a file called helloworld.c
<pre>
#include <stdio.h>
main() {
printf("Hello world
");
}
</pre>

Now to build the program.

cc -o helloworld helloworld.c

You should now have an executable program called "helloworld" of about 7000 bytes. Move this onto your radio and execute it from the command line. You should see "Hello world" and the prompt.

'''Please note''' We haven't used the radio specific library here so your text will not appear on the radio's display, just the telnet session.

At this point you've proved the crosscompiling tools are working fine.

{{NoteBox|<b>Hint:</b><br>if you get the error 'crt*.o: No such file: No such file or directory' while compiling the hello world program, you could try to solve this problem by issuing following commands:
# strace -f -o foo.log arm-9tdmi-linux-gnu-gcc helloworld.c
the log file will contain the information where the compiler is looking for the missing file(s).
Then you can add some symbolic links if you find the file(s) elsewhere. E.g. this command could solve the problem w/ missing crt1.o:
# for i in `ls $RESULT_TOP/build/arm-9tdmi-linux-gnu/gcc-4.1.0-glibc-2.3.2/build-glibc/csu/crt*.o`;do ln -s
# $i $RESULT_TOP/build/arm-9tdmi-linux-gnu/gcc-4.1.0-glibc-2.3.2/gcc-core-prefix/lib/gcc-lib/arm-9tdmi-linux-gnu/3.3.6/${i##*/};done
but you may need to adapt it slightly}}

== Building packages ==

Crosscompiling is easy these days, even with most autoconf/automake configurable packages. The following works for me

* Create a directory where you want to put the fresh compiled libraries, header files and binaries. For example

# mkdir -p /tmp/reciva/root

* Make sure the toolchains 'bin' dir is in your path (as described in [[Toolchain]])

* Configure the package, using the cross compiler and optional previously installed libraries and headers

# export LDFLAGS="-L/tmp/reciva/root/lib"
# export CPPFLAGS="-I/tmp-reciva/root/include"
# ./configure --prefix=/tmp/reciva/root/ --host=arm-softfloat-linux-gnu "$@"

* If all went well, configure should finish without problems, and you can now build and install the software

# make
# make install

Watchdog

2025-06-08T13:05:38Z

Philipp:

== Overview ==

The [[Libreciva]] dog function provides control of the processor's watchdog timer.

In order to use the library function, you must include the header file:

<pre>
#include "dog.h"
</pre>

=== int dog_init() and void dog_exit() ===

These functions are used to initialise and shut down the watchdog system. dog_init() returns true on success, or false if there was an error accessing the hardware.

Note that dog_exit() simply leaves the watchdog in whatever state it has been set - if you want the dog disabled, you must call dog_disable() before calling dog_exit().

=== int dog_enable() and int dog_disable() ===

These functions are used to enable and disable the watchdog. the functions return 0 on success, or -1 if there is an error accessing the hardware.

=== int dog_isenabled() ===

This function reports the current enable (true) or disable (false) state of the watchdog. Note that this function simply reports which dog_enable() / dog_disable() function was last called from this application. It is not possible to read the enabled status back from the hardware.

=== int dog_kick() ===

This function is used to kick the dog. It returns 0 on success, or -1 if there has been a problem accessing the hardware.

ALMHX AlarmClockTime

2025-06-08T13:04:46Z

Philipp:

= ALMHX_AlarmClockTime.txt =

== File Format ==

The file contains a number of rows (one for each alarm). Rows are in the format:

hh:mm t cccccccccc w a o

* hh - Hours to display for alarm time
* mm - Minutes to display for alarm time
* d - Day of week (0=Sunday, 1=Monday)
* cc - Unix time for alarm time (assumes always on GMT!)
* w - 0=Once, 2=Daily, 3=Weekly, 4=WeekDays, 5=Weekends
* a - 0=Buzzer, 1=presetAlarm.txt, 2=presetAlarm1.txt ...
* o - 0=off, 1=on

Example:

07:15 5 1209712500 4 1 1

Alarm On and set for 07:15, at Midnight on Sunday/Monday, Alarm Once, and use Buzzer.

== Direct Manipulation of File ==

If this file is edited outside of the ir application (e.g. directly from a webserver), the ir application ignores the changes.

Following an external update, the ir application must be restarted, either by a radio reboot, or by using "init 3 ; init 2" in a script.

== Calculating cccccccccccc ==

The radio uses and maintains this number to work out the actual alarm time, so it must be correctly calculated each time it is changed / updated. This means that we need to know the current time.

The ir application performs its own time management, and the operating system time is left back in the 1970s. There is no rdate program compiled into the OS.

Be aware that the radio ignores timezones, and actually adjusts GMT when the clocks move on/back - consequently, the cccccc value is the local time, and is not GMT as would normally be expected.
<pre>
#include <stdio.h>
#include <sys/time.h>

main(int argc, char *argv[]) {
time_t t ;
if (argc!=2) {
printf("ctime cccccccc
") ;
exit(1) ;
}
t=atoi(argv[1]) ;
printf("%s",ctime(&t));
}
</pre>
The above function returns the following, when supplied with 1209712500:

On the Radio: Fri May 2 07:15:00 2008
Under Cygwin: Fri May 2 08:15:00 2008

== Writing a web-based Alarm management page ==

In order to write a web-based Alarm manager script, the following tools are needed:

* Get correct network time (rdate type program)
* Convert hh:mm to a real unix time (undoing timezone adjustments done by the ir application)
* Identify the current day (0=Sunday ...)

Alternatively, a web-based Alarm manager application could be written instead of a script. In this case, some steps shouldbe avoided to prevent repeated ntp requests (perhaps by managing the synchronisation of the unix clock)

Whistlist

2025-06-08T13:00:51Z

Philipp: Redirected page to Wishlist

#REDIRECT [[Wishlist]]

Magicbox

2025-06-08T13:00:26Z

Philipp: Redirected page to IMP Magicbox

#REDIRECT [[IMP_Magicbox]]

IMP

2025-06-08T12:59:55Z

Philipp: Redirected page to IMP Magicbox

#REDIRECT [[IMP_Magicbox]]

AE

2025-06-08T12:58:33Z

Philipp: Redirected page to AE Wifi Radio

#REDIRECT [[AE_Wifi_Radio]]

IR100

2025-06-08T12:54:59Z

Philipp:

== Radio ==

The IR100 contains 3 PCBs, the power converter PCB, the Amplifier PCB and the barracuda host PCB, into which is plugged a barracuda module, and a RaLink USB wi-fi adaptor.

There is an [http://logikir100.tripod.com/Logik.htm external owners site] with lots of IR-100 information.

== Radio Firmware/Software Modifications ==

Several owners have used this project to change the firmware on their radios, providing additional features over the official upgrades. (Jan 30th 2008, new official firmware released, check this first before deciding if you need to update your radio using these methods). See [[Changing Your Radio]] , [[Enabling Login]] and [[Changing Firmware]].

== Radio Hardware Modifications ==

A number of modifications have been undertaken on the IR100:

* [[Installing an External USB Socket on the IR100]]
* [[Moving the USB Wi-Fi dongle on the IR100]] and an alternative USB socket
* [[Modifying time delay when starting a track]] Removing the "thump" when radio changes tracks and fixes the missing few seconds at the start of a track. There may be a (partial?) [[Config.txt File]] software fix for this problem.
* [[IR100 Back Rotation]] Fix the speaker hum !
* [[Installing an Ethernet LAN connection]], external USB memory stick connection, mains switch

Still to be documented on Wiki:

* [[Installing an Infrared Remote Control on the IR100]]
* [[Adding a JTAG Port to the Barracuda Module]]
* [[Adding a Serial Port to the Barracuda Module]]

(Please add other modification documentation, such as enabling the USB memory stick for "demo mode" )

== PCB ==

The Barracuda PCB plugs into a motherboard within the IR100. The following image is a composite, showing both the top and bottom PCB layers.

{|
| [[Image:IR100-Motherboard-Layers.jpg|thumb|IR100 Motherboard]]
| [[Image:Ir100_608mr7.pcb.jpg|thumb|IR100 Motherboard version:608mr7]]
|}

== Connectors ==

There are three edge connectors on the Barracuda board (J1, J2 and J3). The pin naming in the image below has been extracted from the IR100 motherboard silk screen.

[Image:Barracuda-Information.xls|thumb|Barracuda ICD Spreadsheet]

== USB ==

There is something odd about the way the USB connection has been made. The IR100 connects the USB D+ and D- with 22R series resistors, and also, each pin has a 15K resistor, which is also connected to ground on the IR100 motherboard.

A bus-master requires two 15K pull-down resistors.

For a bus slave there should be a 1K5 pull-up to 3V3 on either the D+ or D- line (depending on the requested bus speed).

It is possible that this single port can be configured as either a master or a slave (Pin M10 is DP1/PDP0, Pin N11 is DN1/PDN0 - i.e. DP1&DN1 are the Host Functions and PDP0&PDN0 are the Slave Functions, sharing the same pins).

From the source code reciva_usb.c file, it suggests that the driver powers up with the USB interface in slave mode - this should be detectable by monitoring the USB VCC during power-up.

It seems likely that the convoluted interconnection is provided so that the Barracuda module can be plugged into a test configuration, which configures the port as a slave. It seems unlikely that this will be possible in the radio without hardware modification to the motherboard.

Some time during boot, the USB VCC should appear, once the Barracuda board has detected (somehow) that the motherboard wants a USB master.

Some things to try:

* Monitor the USB VCC during reset, and demonstrate that it does infact 'come up' during the boot sequence.
* Power up the barracuda module without the motherboard, without the 15K pull-downs and without the additional ground connections, to try and force the board to be a slave.

[https://www.sharpfin.org/images/b/be/Barracuda-Schematic-Top.pdf Barracuda-IR100-USB.pdf]

==The Software==

The IR100 is running Familiar Linux, and incorporates the Helix DNA player (neptune 1.3) with some additional plugins and a top-level client, written by Reciva.

== Building A Debug Board ==

[[DebugBoard]] Building a Debug Board

File:IR100 with USB-hub.jpg

2025-06-08T12:53:34Z

Philipp:

Config.txt File

2025-06-08T12:51:51Z

Philipp:

== Introduction ==
[[Radios]] have a configuration file, which is named ConfigXXXX.txt, where XXXX is the hardware number of the radio, which you can find with 'Configure / Version'. For example, an IR-100 is 1012. The [[Radios]] page has known hardware numbers.

The configuration file can be changed to enable/disable certain features. Some of these may add a feature a particular user finds useful. For example, those using the alarm clock may prefer it to be higher in the menu structure, or the history feature might be useful to get back to a recent stream.

In addition to enabling / disabling features, the configuration file also tells the radio which software modules to load. These include network drivers, lcd display drivers etc... If you change these entries, it is possible that your radio will be unable to boot / unable to start the network / unable to display things on the lcd display. '''please DO NOT simply copy another config.txt file over the top of yours, hoping that your radio will take on the features of another manufacturers - the answer is that it will, including trying to load the wrong drivers'''

Apply the sharpfin patch, see [[Enabling Login]]
Basic concepts and introduction, see [[Changing Your Radio]]
* Log into the radio using telnet (user & password = admin)
* Look in(''''chdir /root/hwconfig/'''') /root or /root/hwconfig, depending on the current firmware version of your radio
* Find your configxxxx.txt file (The xxxx is the Hardware Id, which you can find in 'Configure / Version')
* Look in it and others in the same directory to work out what modifications you wish to make (such as enabling alarms)
* Issue the command''' 'mount / -orw,remount' ''' to unprotect the partition
* Edit the configxxxx.txt file with''' 'vi configxxxx.txt' '''
* ''' 'i' ''' to enter Insert mode
* Double Check your edits
* Now treble check them!
* Hit <ESC> to leave Insert Mode and enter Command mode
* ''' ':w<ENTER>' ''' To write current file (if you are sure and wish to save it)
* ''' ':q!<ENTER>' ''' To exit 'vi'
* Write protect the drive with''' 'sync;mount / -oro,remount' '''
* Reboot the radio

== Config Overriding ==

The radio application (ir) has the ability to make ammendments to the configuration dynamically. Basically what happens is that on launch, the file /root/config/DSCO_ConfigOverride.txt is downloaded by a function in ''dynconfig_override.c'' and created (if it does not already exist). The ir application then exits, and it is left for the operating system to re-launch it.

For more information on this file, see the [[Config Override]] page.

== Example Config Files for different Radios ==

Click here [[config_example_files]] for example config files with comments and add your config file if it's missing.

== Comments on the Config.txt file ==

Simbo has provided a list of lots of the Configuration Variables here: [[Config_Options_List]]

Space for commented config.txt file (can others add information as it is known and relevant comments please )

Confirmed edits to /root/hwconfig/config1012.txt on a Logik IR-100:

Option:
stations-history
on

Option:
history-size
20

...shows the last 20 streams listened to. History info gets stored in: /root/config/PRE_history.ini, and persists after a power cycle.

NOTE: I tried adjusting the value to 99, with no apparent ill effects with FW.257-a-421-a-057, the file has added a couple of stations quite happily. I know it is a bit of a jump, but might it be possible for Sharpfin to use this file, or another in the same part of the device, as an on board directory of 500 or so popular stations?

Option:
stations-substring-search
on

...Adds 'SEARCH' to the stations menu, allowing searches for stations via letters of the alphabet.(m0aur)

Option:
sleep-timer-upper-limit
86400

...increases sleep timer to a maximum of 24 hours. Value in seconds (M0AUR).

Option:
sleep-timer-increment
300

...Adjusts sleep timer increments in seconds. 300 secs = 5 minute increments.

Option:
standby-text
YourTextHere

...replaces the 'Reciva Radio' text in standby. Use of UTF-8 encoded text in the private which is defined as special symbols in the reciva LCD driver (published by reciva as part of the GPL kernel source) is known to brick the radio. Other non-ASCII text may also have this effect, and there may be a length limit, so you should have a backup strategy before venturing beyond simple short ASCII sequences. 'Internet Radio' which is 14 charaters is OK. DO NOT APPLY STANDBY TEXT EDIT TO MAGICBOX IMP ADAPT TO REPLACE 4 LARGE CLOCK CHARACTERS, IT WILL BRICK THE RADIO! (m0aur)

Option:
clock-in-config-menu
on

...adds Clock in Configure. - Did not appear when used with Firmware v. 257-a-421-a-057
Showing here with FW 257-a-421-a-057 [[User:Simbo99|Simbo99]] 22:58, 20 January 2008 (CET)

Setting this string to OFF places the alarm and sleep functions on the top menu.

Option:
clock-dst-menu
on

...adds DST(„Daylight Saving Time“) On/Off to Clock menu.

Option:
clock-format-menu
on

...lets you change from 24hr to AM/PM - Clock will default to 24hr if there is an active alarm.

Option:
stereo-mode
stereo

Option:
stereo-mode-menu
on

...this adds a Stereo menu in Configure with Stereo/Mono options.

Option:
aux-menu
on

...this adds the menu option Equalisation under Configure & with Treble -14/+14 and Bass -14/+14 - it did nothing to the treble/bass on an IR-100 & IPdio (962).

Option:
contrast-menu
on

...adds the menu option Contrast under Configure & counts up/down with the wheel, doesn't alter the contrast on an IR-100.

Option:
volume-control
on

Option:
initial-volume
28

...whilst listening to a stream, the wheel alters the volume with an on-screen graphic to indicate min/max Volume. Not much use on an IR-100 - which has the audio-amp volume knob. - Easiest to use with 'official' volume control at maximum and use select knob only - NOTE: This leads to a slightly audible background crackle even at low volumes.

I believe the 'initial-volume' refers to the volume of the alarm, changing the value does not appear to have any effect on an IR100 with 257-a-421-a-057 FW.

The initial-volume is the software-volume level when the radio comes out of standby.[[User:Simbo99|Simbo99]] 22:58, 20 January 2008 (CET)

I have tried initial-volume values from 28 to 99 on both the LOGIK IR100 and the Tangent Quattro, Both radios still come out of standby at the last used volume level. Despite the scroll wheel showing a varying volume graphic on the Tangent Quattro, it does not actually alter the volume. (M0AUR)

Volume control displays graphic on Revo Pico but does not behave as expected. Volume is not affected unless 0 is selected which mutes the radio --[[User:Goldstien|Goldstien]] 15:39, 24 June 2008 (CEST)

( Please edit / add more configuration options as known )

From "grepping" through the configxxx.txt

Option:
alarm-clock
off|config1|config2|no-alarm

off: no clock at all, no-alarm: just a clock, no alarm. config1&config2: alarm clock functionality enabled, difference between settings not yet known. '''config1' = alarm goes straight to radio without buzzer (IR100 257-a-421-a-057)''

Option:
number-of-alarms
5

This allows you to set multiple alarms and choose weekdays, weekends etc and whether to use the buzzer or a preset - NOTE - Any selected preset must remain tuned to the same channel for the alarm to continue to tune to radio - NOTE - All alarms start with a buzzer, which sounds for 20-30 secs and then tunes to a chosen station, which as to be selected from the 5 presets - Can be switched at will by pressing the Select knob. Buzzer can be disabled by using the alarm clock/config2 hack above.

Increasing the number of alarms in the config1012.txt file of the Logik IR100 running the latest 057 service pack will no longer work, as upon station update, the Reciva site edits the value back down to 2, which is now standard.
I think it is done via a 'watchdog s3c2410' command within the /mnt/ramfs/tmp/config1012.txt config1012.txt.withparams. It can also be found in the /mnt/config/DSCO_ConfigOverride.txt, and the /root/config/DSCO_ConfigOverride.txt files. These all seem to link to the /proc/s3c2410-break-hack file. So Reciva seem to be actively blocking some edits. (M0AUR)

Option:
power-on-select-key
on
This allows a select spinner press to turn the radio on. Does not work on Tangent Quattro.

Option:
menu-timeout
10
This controls how long a menu is shown before dropping back to the now playing screen

Option:
back-as-menu-item
on
Adds a <<Back option to every menu

Option:
presets-as-menu-items
on
This shows Twelve presets in "Stations" list. To store a station on any of the presets: Listen to a stream, go (back) to "Stations", scroll to an empty preset, long press on the select spinner - station stored. To listen to a station on these new presets: From "Stations", scroll to desired preset then short press select spinner.

Option:
off-in-main-menu
on
This shows an off option at the bottom of the main menu

Option:
long-select-action
popup

This enables an equalizer menu accessed with a long press of the Select button - Note this is visible but completely non functional on the IR100.

Option:
snooze-key
power

This option produces a 5min snooze on the alarm when you press the power key, I guess it could be mapped elsewhere, the alarm time shown in brackets advances 5 mins to confirm,

IR100 - FW v.257-a-421-a-057 - This works, but makes switching off by the power button rather difficult - the radio seems confused as to what it is supposed to do, press once and sound will break up for about 30secs before powering down.

I also detected a change in the level (up) of the transformer hum while trying this one.

Option:
force-metadata
on

Depending on the station/stream etc, you get track and artist information as a scrolling line - directly after the "REAL ENABLED" it will read something like "REAL ENABLED - xxxx artist - xxx track" This is ''totally'' dependent on the stream/podcast station and what they decide to transmit.

Option:
show-busy-bar-on-samba-scan
on

Shows a busy-bar instead of filenames as samba scans a share for media.

Option:
acpoweron-state
network

...on AC power on, radio connects to network then goes to standby, staying connected to network. Only works if "Go to standby after power cycle" under 'My Radios' on the Reciva site is *unticked*. This option is good in the event of an overnight power cut, it stops the radio connecting to the last played station upon reconnection.

Option:
dynamic-mute
off

...''(Can someone else try this & confirm then delete/edit this text - taa [[User:Simbo99|Simbo99]])'' Keeps the audio amp powered on, so doesn't chop first few seconds of MP3s. Makes [[Modifying time delay when starting a track]] redundant?

Cannot comment on mp3s from PC, but it does look like it works! I logged onto an MP3 stream which plays a set file (beatlesradio.com) before you get the stream and for the first time, had the whole thing! (Tried on two IR100s with 257-a-421-a-057 FW.). A comment on the discussion list from "JohnR" suggests that this is not a total fix; it alters things, but there is still a loss of a few seconds at the start of tracks from a Twonky media server (which does not have the delays when used to other devices).

I noticed this problem with Twonky (it would miss off the first 15 secs of each track. I then tried TVersity and this seems to work perfectly (just need to set the Media Playback device as "Windows Media Center").

BAD news about this one, IR100 FW 257-a-421-a-057 - after a couple of days, I noticed a background crackling, which I could
not put up with, after editing this config out, it dissapeared, It is worse when the radio is silent, for example when
searching for media,butseems to be there all the time, also very noticable on Radio 4, which seems to have a hiss of its own
as well. The problem was worse on one radio than the other, so some may possibly not have it at all. I don't know much
about electronics, but my best guess is that the config was set up in the original way to hide a quality control issue at
the factory.

I noticed this crackling on an unmodified IR100 when listening to quiet audio (eg Radio 4 or Radio 3). I then noticed that the crackling sound corresponded exactly to the activity light on my WiFi access point - it was the WiFi dongle impacting on the speaker (like the transformer hum problem). I moved the dongle to the other side of the radio and this removed the crackling noise. The above config mod works a treat .... I've been using my IR100 with TVersity to listen to audio from my PC and the 'dynamic-mute off' has cured the 3 second mute at the start of each track. Good work you guys.

When turning dynamic-mute off, you can no longer mute your radio with the mute button on the remote control (applies at least for ipdio Style)

Option:
long-browse-press-clears-media-queue
on

...While streaming media from a PC, this allows you to clear the media queue without having to go back up the menus. Very usefull if you stream media!

Option:
hierarchical-locations
on

Organizes the station browser into the not very loved 'continent' order.
Answer: Is there a change on the IR100?--[[User:Tim|Tim]] 20:12, 22 January 2008 (CET) - If you are running FW v.257-a-421-a-057, which misses the continent step out [[rfcvb72]] 19:19, (GMT) 22 January 2008

Option:
preset-poweron
on

Any preset switches on the radio from standby, but infuriatingly only opens the top menu, so pretty much useless until someone can work out another command (if there is one) to make it tune straight to the desired station. (IR100 v.257-a-421-a-057)

Option:
scrobbling
on

No effect at all on and IR100 v.257-a-421-a-057 , but no harm either. I think that this may be intended for devices which include an ipod dock, as LastFM features 'Scrobbling' of ipods.

Option:
deemphasis-menu
on

Option:
deemphasis-menu-values
0 44100
This adds a 'Deemphasis' item to the Configure menu, with the settings of 'none' and '44.1kHz'.
Using the above values on the Tangent Quattro, produces a deemphasis menu which contains the options 'None' '32kHz' '44.1kHz' and '48 kHz'. (M0AUR)18:46 8th Feb 2008.

Why would you do this you might ask? Well there's a bug somewhere, maybe in the driver for the Wolfson WM8721 DAC.
The de-emphasis register in the DAC is being written to somewhere, and going into this menu and selecting 'none' clears the register and turns off de-emphasis which should not be on in the first place. De-emphasis is something DAC chip makers provide for compatibility with a handful of very early CDs that had pre-emphasis (a treble boost) applied. De-emphasis causes a massive treble reduction and should not be on! According to the DAC data sheet, with it on, the treble is down nearly 10dB at 20kHz which is like turning the treble right down on your amp. The makers of the Logik sets, Hip Shing, (over)compensated for this in the IR-100 with a treble boost in the amplifier so nothing needs to be done here (unless you want a treble boost control) BUT they didn't bother on the IRMA1 which sounds hopelessly muffled. With this tweak in config997.txt it sounds absolutely fine. The only bad thing is I haven't found out how to set a default. If you power-cycle you have to set it again (though from Standby you do not so not a big deal). There is a 'deemphasis-frequency' option too, which I tried setting to '0' but it had no effect.
Tested on IRMA1 and IR-100 both with v257-a-421-a-057. Stolen from config854.txt. --[[User:GSUM|GSUM]] 18:51, 27 January 2008 (CET)
Option:
super-scrolling
on

Option:
super-scroll-remote-start-delay
2

Option:
super-scroll-remote-scale-factor
1

Option:
super-scroll-remote-max-step-rate
10

Option:
super-scroll-remote-repeat-threshold
400000
This is VERY handy for the IRMA1 which lacks a rotary selector. (config997.txt)
Scrolling through hundreds or even thousands of stations by just holding the << or >> buttons down is impossible - you just lose the will to live. With these options, if you hold the button in for a couple of seconds, it starts leaping 10 entries at a time. Makes the unit MUCH more usable! Tested on IRMA1 with v257-a-421-a-057. Stolen from config854.txt. --[[User:GSUM|GSUM]] 18:51, 27 January 2008 (CET)

Option:
reset-clock
on

This adds a 'Reset Clock' option to the clock menu, it appears to force a sync with the time server. IR100 with v257-a-421-a-057 (Unofficial)

EDIT: The manual for the Sangean (which has this feature as standard) infers that this function removes any user alteration (DST changes etc) but does not specifically mention resync with the server.

Option:
usb-thumbdrive
on

Option:
thumbdrive-power-connector
2

Option:
thumbdrive-power-pin
30

Option:
local-media
on

...Adds 'Local Media' in 'Media Player' menu. Plug in a thumb-drive with media on it, then power-cycle. Suggest: Add an external USB hub & velcro it to the back of your radio. Just like [[https://sharpfin.org/index.php/Image:IR100_with_USB-hub.jpg this picture]]

Option:
media-player
off

Removes the 'Media Player' link from the main menu - obviously this will make the media streaming function useless as well.

Option:
reply-button-exits-spinner
on

In the scrolling character entry lists, for instance when entering a WiFi key, this allows a press on Reply instead of scrolling to the [END] option and selecting it. This is probably part of the default configuration for your radio, but was needed to restore this function with the 257-a-744 beta firmware.

----

'''The following settings have only been tried in 257-a-756-a-199 beta firmware....'''

Option:
pbch-report-enabled
off

Removes the "REAL ENABLED" text from the stream information

Kernel Module: reciva_lcd_generic line1frame1="Radio" line2frame1="powered" line3frame1="by" line4frame1="sharpfin" line1frame2="Keep on" line2frame2="rocking" line3frame2="in the" line4frame2="free world"

Replaces the "Reciva Radio" and "ARM powered" startup text. DO NOT simply enter "" as this causes a startup failure, use " " for a blank line.

== Changes to /root/hwconfig/all_radios.txt ==

Most if not all models seem to refer to this file in their main config, so it's contents are presumably referenced as if they were in the main configxxx.txt

Option:
reply-button-function
on

Pressing the reply button when tuned to a stream calls up an add to favourites menu, which adds the stream to 'My Stations' on the radio and your Reciva account.

It may work if you place it in the main configxxx.txt for your radio, but I have not tested it.

Tested on a IR100 with v.257-a-421-a-057 firmware, the text was already there, I just had to change the instruction from 'off' to 'on'

The only radio I know of with this feature as standard is the Tangent Quattro with up to date firmware.

== Suggested combinations for various radios ==

The following known to work well and provide sensible User Interface benefits to Radio owners:

'''IR 100 with firmware 257-a-421-a-057'''
''(Can someone enter a set of sensible suggestions ?)''
^
Max:
clock-dst-menu:on | back-as-menu-item:on | number-of-alarms:5 | alarm-clock:config1 |
back-as-menu-item: on

"number-of-alarms" is very useful

Rfcvb72 - IR 100 with firmware 257-a-421-a-057 - I have these mods running on two IR100's at the moment
clock-dst-menu:on | back-as-menu-item:on | number-of-alarms:5 | alarm-clock:config1 |
back-as-menu-item: on | off-in-main-menu: on | stations-history (20)| power-on-select | dynamic-mute: off |

And in /root/hwconfig/all_radios.txt:

reply-button-function: on

The only problem I have had is with the snooze function on the power button, which caused shutdown problems, might work better if mapped to another button, but then if you cant find the button, why have a snooze function?

Favourites are: number-of-alarms:5 | alarm-clock:config1 | power-on-select | dynamic-mute: off
all of which make a real difference to the user experience.

'''Bookmarks'''

Bookmarks are a usefull function that allows you to add favourites to a menu in the radio section. This can be added and deleted locally on the radio (unlike the My Stations feature that can only be added locally using the reply feature). I've only tested this with 257-a-756-a-030 on an AE, but will presumably work on all radios with this version of the firmware.

To turn bookmarks on:
Option:
bookmarks
on

To make it possible to add the current station to the bookmarks:
Option:
bookmark-on-long-select
on

or (depending on preference, although I have only tried the long select option)

Option:
bookmark-on-short-select
on

When you select a bookmark you will be given the option to play or delete from the list

'''Ipdio Style with firmware 257-a-756-a-183'''

Option:
dynamic-mute
off

Strongly recommended. Turns off the 3 sec delay and the cracking noise between tracks when playing mp3 from your upnp server. This was a big hassle for me, thanks to the sharpfin guys for solving this! When turning dynamic-mute off, you can no longer mute your radio with the mute button on the remote control!

Option:
reply-button-function
on

Strongly recommended. Add current station to MyStations at your reciva account.

Option:
long-browse-press-clears-media-queue
on

Sounds like a nice function to me.

Option:
report-empty-presets
on

Shows a message instead of doing nothing when pressing an empty preset key.

Option:
clock-format-menu
on

Option:
bitmap-clock
64x64 /usr/share/reciva/clockdata.bin

Enables cool looking analog clock, but did not show the correct time.

Option:
split-alarm-icons
on

Different Icons for different alarms.

== How to turn off wireless on standby ==

NOTE: 20th March 2008

This Hack seems to be redundant as of FW v.257-a-615-a-075, which applies this powerdown feature as default (tested on IR100)

----

Note: September 10, 2008

This "feature" that now is also included with firmware v257-a-756-a-030 causes a new problem where the radio does not connect to the network after a power outage to get its time updated. This causes the clock to reset to midnight in Standby mode and is not a good idea for a radio used as an Alarm Clock. See this thread on reciva.com:
https://www.reciva.com/index.php?option=com_joomlaboard&Itemid=108&func=view&catid=3&id=23869#23869

----

As noted on Bill888's support page, the Ipdio (962) uses less power on standby (2.9 watts vs. 7 watts), due to it's wireless being switched off.

A quick look through config962.txt threw up the following:

# --------------------------------------------
# Turn off wifi power in standby - start
# --------------------------------------------

Option:
soft-power-down
mode2

Option:
wireless-ethernet-connector
2

Option:
wireless-ethernet-pin
32

# --------------------------------------------
# Turn off wifi power in standby - end
# --------------------------------------------

I pasted this into config1012.txt, below the last 'Option' string and above the driver info and now my wireless is off when the radio is on standby, the dongle usb does not blink and I cannot ping from a command prompt or access the Sharpfin webserver.

Interestingly, the radio seems to switch on to connect and switch off much quicker now, which seems a bit contrary.

Presumably it is using less power as well, though I don't have a meter to test it with. It will be intersting to see if the radio uses less power switched on as per the ipdio as well.

This also has the benefit for those of us with external dongles of not leaving a hot, powered up dongle where little hands can find it when the radio is not in use.

ADVICE: IF YOU WANT TO COPY/PASTE THIS, COPY IT OVER FROM config962.txt TO config1012.txt FROM ONE VI WINDOW TO ANOTHER. COPYING IN WINDOWS TEXT FORMAT DOES NOT SEEM TO WORK.

AND MAKE SURE YOU CHECK IT!

Note: I've tested it with a lan-adapter[cable] and it's working great! (Radio:IR100) --[[User:Tim|Tim]] 20:33, 22 January 2008 (CET)

'''After changing "soft-power-down","wireless-ethernet-connector","wireless-ethernet-pin":<br>'''
Power consumption(230V):<br>
Working->Volume=min ->47,7mA<br>
Working->Volume=max ->approx 60mA(depends on radio station/programm, tested with BBC1<br>
Standby ->41,1mA<br>
Unplugged the lan-adapter-> 41,1mA<br>--[[User:Tim|Tim]] 21:51, 22 January 2008 (CET)

'''An easier way to achieve this result:'''

include the line 'include config962.txt' in the config file of your radio. Config962 itself includes the line 'include config1012.txt' it would seem prudent to remove this, especially if you have an IR100 or similar.

NOTE: adding this line will also enable Stations History, Hierarchical Locations and Standby Text (Ipido Radio)

== Podcasts in top menu ==

I just put this section in as a teporary measure to log attempts with this string, so we dont need to waste our time repeatedly trying the same values, it could doubtless do with a table if anyone knows how to knock one together.

podcasts-menu-position

'top' > tried with v257-a421-a-057 > no effect

'main' > tried with v257-a421-a-057 > no effect

== Further notes and observations ==

This [https://www.reciva.com/index.php?option=com_joomlaboard&Itemid=77&func=view&id=12143&catid=3 thread] on the Reciva website has a few clues ( which may now all be explained above ).

<nowiki>*** For Tangent Quattro owners ***

I tried some mods on the config931.txt. But after today's change I have bricked my radio....
I am running these software/firmware versions:
v589-a-516-a-055;257-a-421-a-041;v24070821+00-a-012
One of these two mods causes the radio not to boot.

Option:
playback-layout
clock-plus-1line

[I had hoped to enable the clock when listening to radio or media server]

Option:
long-browse-press-clears-media-queue
on

So now I have to unbrick it! Just ordered the JTAG cable.
When I have it and started to disassemble my Quattro MKII I will keep you posted.

Bernard</nowiki>
<nowiki><nowiki>Insert non-formatted text here</nowiki></nowiki>

Questions

2025-06-08T12:51:07Z

Philipp:

== Questions ==

Some questions that come to mind when gathering the info

* There seems to be [[LIRC]] support in the kernel, reciva also provides lirc sources. How hard would it be to add a remote to existing radios ?
**It's very easy, I've got one working on a Logik IR100. All radios include LIRC but the configuration file needs to be changed so shell access is necessary. --[[User:Rdk|Rdk]] 16:49, 21 August 2007 (CEST)
* What is the purpose of the libgpg-error package Reciva provides ? Is this just used as a generic error reporting framework?
**Presumably libgcrypt depends on it.
* Does the Barracuda use special co-processors or dedicated hardware for audio codecs ?
**The audio codecs are all implemented as software libraries, new ones have been added over time e.g. aac+ and now FLAC --[[User:Rdk|Rdk]] 16:49, 21 August 2007 (CEST)

== Letters ==
Hello,

I added a usb hub to my IR100. An usb ethernet adapter and the original wifi adapter are plugged into that hub.
My problem is that the devices(hub,wlan/ethernet adapters) don't turn off when I switch off the radio(standby)

If the ethernet or the wifi adapter is connected without a hub to the reciva board, the devices turn off if I switch off the radio.

Does anyone has an idea how I could solve that problem?

I also tried changing that option "soft-power-down"->mode2(default) to mode1
--[[User:Tim|Tim]] 02:09, 8 March 2008 (CET)

----

Hello,

is it possible to add an optical audio out to the reciva radios (esp. ipdio Style)? At least with my radio, the analog headphone output is of very low quality and there is a clearly audible noise at low volumes.

Thanks,
kom

--[[User:Kom|Kom]] 10:40, 11 September 2008 (CET)

----

Hello,

after i changed my Config849.txt, my radio doesn't boot, when i turn it on, it displays "Reciva Radio ARM Powered".
I don't have a JTAG cable, and i don't have a backup file.
But can i use a USB keyboard attached to the internal USB port to close the Reciva application (like ALT + F4 in Windows) and wait to the Sharpfin telnet server loads, to use telnet to restore the original Config849.txt file ?

--[[User:Andrei66|Andrei66]] 12:32, 23 March 2010 (CET)

Hardware

2025-06-08T12:49:47Z

Philipp:

= Radios =

The Barracuda is used in [[Radios|these radios]].

== Hardware Matrix ==

The radios contain slightly different internal hardware architectures, including different LCDs, Keypads and some different pin connections on the Barracuda module. A [[Hardware Matrix]] showing the differences, plus datasheets for the hardware has been compiled.

= Barracuda hardware =

The Barracuda module is a pretty straightforward, but very compact, board with CPU, flash, ram and some interfacing for audio, buttons and LCD display

{|
| [[Image:barracuda-top.jpg|thumb|Front of the PCB]]
| [[Image:barracuda-bottom.jpg|thumb|Back of the PCB]]
|-
| [[Image:Barracuda-board-outline.jpg|thumb|Board outline with numbered pins including JTAG]]
| [[Image:Processor-pin-types.jpg|thumb|Processor Pin Types]]
|-
| [[Image:barracuda-pinout.png|thumb|Connector pinout, thanks to rdk]]
|-
| [[Image:Barracuda-layers.jpg|thumb|Composite image showing top and bottom layers]]
|-
| [[Image:Barracuda.jpg|thumb|Original and later Lead-Free versions]]
|}

The Processor board is marked 'Reciva' and 'IRM2' in the silk screen, and contains (mainly) three devices, all manufactured by Samsung.

The next row of images shows a board outline with pin numbers on the pads. These numbers are by no means official, but until we know the exact purpose of the pins, it's handy to give them a number so everybody is talking about the same thing. Reciva's application note for the Barracuda module is at http://www.reciva.com/data/barracuda_1.6.pdf. It contains the official pin numbers and descriptions.

== Diagnostics ==

Diagnostic Captures have been taken to diagnose:

* [[Connector Pins]]
* [[Component Pads]]

== Main CPU ==

* The central one is the main processor, [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=836&partnum=S3C2410&xFmly_id=229 Samsung S3C2410] for which a complete datasheet has been available. Samsung recently updated their website, and the datasheet is now only available to registered companies.

The processor is running at 202.80MHz (MPLLCON=000a1031)

The CPU has the following on-board functions:

* ARM920T core
* PCM Sound device
* USB host/device interface
* TFT LCD/STN LCD Controller (16bit, 640x480 maximum)
* JTAG Port (is TRST Open Drain or Push Pull?)
* ...

== Smally Tiny12 CPU ==

There's also an [http://www.atmel.com/dyn/resources/prod_documents/doc1006.pdf Atmel Tiny12L MCU] onboard. There is only a rough idea what it is doing.

The sernum daemon uses it to:

* create the DES and 3DES keys for the [http://www.g3gg0.de/wordpress/?p=31 reciva:// protocol] using XTEA cipher. (That protocol is e.g. used to get the playlists from the reciva servers)
* get the serial number of the device
* reset the device (not tested yet)

Atmel is accessed via a simple serial protocol using these ports:
GPE11 - SACK (ARM <- Atmel)
GPE12 - SDAT (ARM <-> Atmel)
GPE13 - SCLK (ARM -> Atmel)

At startup the sernum daemon simply mmaps the memory area at 0x56000000 with size 0x100 to directly access the GPIO's at 0x56000040 and 0x56000044.

Some standalone tool which access the Atmel and reads serial number, version and calculates some example challenges will soon be uploaded into the SVN repository.

Another guess is that it controls the booting of the main processor. The big processors often have built-in boot loaders that are accessed by setting pins high or low at reset. This can be controlled with links, but using a tiny processor makes more sense. It could for instance invoke the boot loader at start-up and check for a few seconds to see if there is any communication. If there is some, it lets the boot continue. If there is none it resets the processor, set the links to run mode and the starts the processor. This is much easier than opening the box and setting links/switches!

== Flash ==

* The top left device is the [[Reciva NAND Flash]], which a [http://www.samsung.com/products/semiconductor/NANDFlash/SLC_SmallBlock/128Mbit/K9F2808U0C/K9F2808U0C.htm K9F2808U0C]: 16Mb*8 flash memory.

== RAM ==

* the bottom left device is [http://www.samsung.com/Products/Semiconductor/Sync_AsyncDRAM/SDRSDRAM/Component/256Mbit/K4S561632E/ds_sdr_256mb_e_die_x4x8x16_rev15.pdf SDRAM 16M*16] (K4S561632E-TC75)

== Schematic ==

This [https://sharpfin.org/images/b/be/Barracuda-Schematic-Top.pdf Barracuda-Schematic-Top.pdf] (work in progress) is an amalgamation of information extracted from several disassembled radios, plus information extracted from the GPL'd source.

== Source Data ==

Source files (schematic, drawings, etc...) can be found on the [[Source Files]] page.

Hardware

2025-06-08T12:47:07Z

Philipp:

= Radios =

The Barracuda is used in [[Radios|these radios]].

== Hardware Matrix ==

The radios contain slightly different internal hardware architectures, including different LCDs, Keypads and some different pin connections on the Barracuda module. A [[Hardware Matrix]] showing the differences, plus datasheets for the hardware has been compiled.

= Barracuda hardware =

The Barracuda module is a pretty straightforward, but very compact, board with CPU, flash, ram and some interfacing for audio, buttons and LCD display

{|
| [[Image:barracuda-top.jpg|thumb|Front of the PCB]]
| [[Image:barracuda-bottom.jpg|thumb|Back of the PCB]]
|-
| [[Image:Barracuda-board-outline.jpg|thumb|Board outline with numbered pins including JTAG]]
| [[Image:Processor-pin-types.jpg|thumb|Processor Pin Types]]
|-
| [[Image:barracuda-pinout.png|thumb|Connector pinout, thanks to rdk]]
|-
| [[Image:Barracuda-layers.jpg|thumb|Composite image showing top and bottom layers]]
|-
| [[Image:Barracuda.jpg|thumb|Original and later Lead-Free versions]]
|}

The Processor board is marked 'Reciva' and 'IRM2' in the silk screen, and contains (mainly) three devices, all manufactured by Samsung.

The next row of images shows a board outline with pin numbers on the pads. These numbers are by no means official, but until we know the exact purpose of the pins, it's handy to give them a number so everybody is talking about the same thing. Reciva's application note for the Barracuda module is at http://www.reciva.com/data/barracuda_1.6.pdf. It contains the official pin numbers and descriptions.

== Diagnostics ==

Diagnostic Captures have been taken to diagnose:

* [[Connector Pins]]
* [[Component Pads]]

== Main CPU ==

* The central one is the main processor, [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=836&partnum=S3C2410&xFmly_id=229 Samsung S3C2410] for which a complete datasheet has been available. Samsung recently updated their website, and the datasheet is now only available to registered companies.

The processor is running at 202.80MHz (MPLLCON=000a1031)

The CPU has the following on-board functions:

* ARM920T core
* PCM Sound device
* USB host/device interface
* TFT LCD/STN LCD Controller (16bit, 640x480 maximum)
* JTAG Port (is TRST Open Drain or Push Pull?)
* ...

== Smally Tiny12 CPU ==

There's also an [http://www.atmel.com/dyn/resources/prod_documents/doc1006.pdf Atmel Tiny12L MCU] onboard. There is only a rough idea what it is doing.

The sernum daemon uses it to:

* create the DES and 3DES keys for the [http://www.g3gg0.de/wordpress/?p=31 reciva:// protocol] using XTEA cipher. (That protocol is e.g. used to get the playlists from the reciva servers)
* get the serial number of the device
* reset the device (not tested yet)

Atmel is accessed via a simple serial protocol using these ports:
GPE11 - SACK (ARM <- Atmel)
GPE12 - SDAT (ARM <-> Atmel)
GPE13 - SCLK (ARM -> Atmel)

At startup the sernum daemon simply mmaps the memory area at 0x56000000 with size 0x100 to directly access the GPIO's at 0x56000040 and 0x56000044.

Some standalone tool which access the Atmel and reads serial number, version and calculates some example challenges will soon be uploaded into the SVN repository.

Another guess is that it controls the booting of the main processor. The big processors often have built-in boot loaders that are accessed by setting pins high or low at reset. This can be controlled with links, but using a tiny processor makes more sense. It could for instance invoke the boot loader at start-up and check for a few seconds to see if there is any communication. If there is some, it lets the boot continue. If there is none it resets the processor, set the links to run mode and the starts the processor. This is much easier than opening the box and setting links/switches!

== Flash ==

* The top left device is the [[Reciva NAND Flash]], which a [http://www.samsung.com/products/semiconductor/NANDFlash/SLC_SmallBlock/128Mbit/K9F2808U0C/K9F2808U0C.htm K9F2808U0C]: 16Mb*8 flash memory.

== RAM ==

* the bottom left device is [http://www.samsung.com/Products/Semiconductor/Sync_AsyncDRAM/SDRSDRAM/Component/256Mbit/K4S561632E/ds_sdr_256mb_e_die_x4x8x16_rev15.pdf SDRAM 16M*16] (K4S561632E-TC75)

== Schematic ==

This [https://sharpfin.org/index.php/Image:Barracuda-Schematic-Top.pdf schematic] (work in progress) is an amalgamation of information extracted from several disassembled radios, plus information extracted from the GPL'd source.

== Source Data ==

Source files (schematic, drawings, etc...) can be found on the [[Source Files]] page.

Logos

2025-06-08T12:44:48Z

Philipp:

== Logos ==

[[Image:sharpfin.jpg]]

Download file [https://www.sharpfin.org/images/d/db/Sharpfin.jpg here]

== Avatars ==

[[Image:sharpfin-avatar.jpg]]

Download file [https://www.sharpfin.org/images/7/76/Sharpfin-avatar.jpg here]

Main Page

2025-06-08T12:43:40Z

Philipp:

= Sharpfin project =

The goal of this project is to gather information about the Reciva 'Barracuda' radio module, in order to understand enough of the hardware to be able to provide alternative [[GPL]] firmware.

The Sharpfin Project <i>needs the support</i> of keen and enthusiatic hobbyist/engineers - it is a mammoth task in understanding the internal workings of the radio - we have some partial schematics and are begining to analyse the [[GPL]] code, but there is lots to do, so

If you would like to participate, or if you have any information to share on this wiki just [{{fullurl:Special:UserLogin|type=signup}} register] or [[Special:UserLogin|login]] and start editing.

Technical / development discussions can be found on the [http://groups.google.com/group/sharpfin Sharpfin Google Groups Pages]. Suggestions for new mailing system are welcome

<table width=100%>
<tr>
<td colspan=2 bgcolor=#ffffff style='border: solid 1px #888' valign=top>
== News ==
* 2017-03-11: A server upgrade was performed and HTTPS support was added. We recommend these URLS: https://www.sharpfin.org or https://www.sharpf.in
* 2012-11-30: Since a few days ago you can reach the wiki also via https://www.sharpfin.org, https://www.sharpf.in
* 2012-10-22: New howto page: [[OpenOCD|Barracuda module debug over JTAG using OpenOCD]]; thx to Dhires
* 2012-10-10: News for [[Unbricking]]/[https://www.sharpfin.org/images/a/a4/Sharpflash_v0.4.zip Sharpflash v 0.4]
* 2012-10-03: [[Releases#Patchserver|Patchserver 0.7rc3]] [https://www.sharpfin.org/images/2/25/Patchserver_0.7rc3.zip Win] (no changes for Linux version)
* 2012-10-01: [[Releases#Patchserver|Patchserver 0.7rc2]] (<strike>Win</strike>/[https://www.sharpfin.org/images/8/85/Patchserver_0.7rc2.tar.bz2 Linux])
* 2012-01-14: [[Releases#Patchserver|Patchserver]] ([https://www.sharpfin.org/images/1/1e/Patchserver_0.7rc1.zip Win]/[https://www.sharpfin.org/images/6/60/Patchserver_0.7rc1.tar.bz2 Linux]), [[Releases#Webserver|Webserver]], [[Releases#Libreciva|Libreciva]] updated & [[Releases#Nanddump|Nanddump]] and [[Releases#Lircd|Lircd]] added
* 2012-01-09: Windows [[Releases#Development Tools|Cygwin Cross-Compiler]] v 0.2 released
* 2012-01-02: Sharpfin [[Releases#Webserver|Webserver]] v0.8 released (remote control integration, etc.)
* 2011-12-31: Sharpfin [[Releases#Webserver|Webserver]] updated (links, nanddump, etc.)
* 2011-12-05: New Sharpfin Wiki
* 2011-11-30: [https://github.com/philsmd/sharpfin Github repo] created
* 2010-11-06: [[Installing an Infrared Remote Control on the IR100]] updated
* 2010-05-14: [[Modifying the Hardware]] section added.
* 2010-03-12: [[Sharpfin Enhance Pack]] 2 - SHARPFINreloaded is out!
* [[Old News]]

</td>
</tr>
<tr>
<td bgcolor=#ffffff style='border: solid 1px #888' valign=top>

=== Project documentation ===

* [[Introduction]]: What's all this
* [[Quickstart]]: For the impatient
* [[Legal]]: Legal stuff
* [[Wishlist]]: What do we want...
* [[Roadmap]]: ...and how do we get there
* [[Libreciva]]: Our libreciva reference manual
* [[Repository]]: The Sharpfin Git Repository
* [[Talk:Main_Page|Discussion]]: A place for talk and chat
* [[Logos]]: Icons, Avatars and Logos
</td>
<td bgcolor=#ffffff style='border: solid 1px #888' valign=top>

=== Technical documentation ===

* [[Radios]]: Reciva Radios and features. Also firmware info.
* [[Hardware]]: What's in the box
* [[Software]]: And what is it running
* [[Changing Your Radio]]: Change configuration and firmware
* [[Modifying the Hardware]]: Hardware modifications for your radio
* [[Unbricking]]: How to recover when things go wrong
* [[Links]] to other sites with info
* [[Questions]]: Things that are unclear and need to be figured out
* [[Sample Project]]: Your home-made Internet Radio Exploration Lab

</td>
</tr>
</table>
<div class="footer_image">[[File:Sharpfin_transparent.png]]</div>

Installing an Infrared Remote Control on the IR100

2025-06-08T12:42:07Z

Philipp:

This applies to all Reciva radios, not just the IR100.

For a remote control to work there must be a suitable IR sensor fitted and a lircd configuration file. That's it!

=== Adding a sensor ===

For radios that don't already have an IR sensor some hardware modifications will be required to add one in the case where it will be visible. Almost any IR decoder that will run from a 3.3V supply should work, these devices remove the 38kHz carrier and output a logic signal that the Barracuda board can directly decode. Most remote controls operate at 38kHz but there are some which operate at higher frequencies which won't work with the sensors listed.

Some suitable sensors available from RS components are:

* TSOP34838 (RS 700-5308)
* TSOP1138 (RS 708-5550)
* TSOP31238 (RS 570-578)
* GP1UX301QS (RS 666-6542)

(Maplin no longer appear to stock anything suitable)

Check the pin-out for whichever model you use - they're not all the same. Connections to the radio are:

* Decoded signal / output - GPG6 (JP1, pin 5),
* Vcc / Supply - 3.3V supply (JP1, pin 14),
* Gnd. (JP1, pin 9)

Pin numbers refer to the Barracuda board itself. It's probably best to solder the wires to the main board inside the radio, rather than directly to the barracuda board so that it can be removed if necessary. Carefully check the connections to make sure the correct pins are used and nothing gets shorted out!

{|
| [[Image:Barracuda-board-outline.jpg|thumb|Board outline with numbered pins]]
| [[Image:barracuda-pinout.png|thumb|Connector pinout]]
|}

A 47nF ceramic or polyester decoupling capacitor connected to the supply pins at the sensor end of the wires is probably a good idea.

=== Configuration to enable control ===

For the radio to respond to an IR remote control a lircd configuration file is required in the /etc/config/ directory. The file must be named lircd_configXXXX.conf where the XXX is replaced with the radio's hardware ID. For a Logik IR100 this would be lircd_config1012.conf

=== Using a Reciva remote control ===

If you have a remote control that works with an existing Reciva radio you can simply copy the file for that, renaming it with your radio's hardware ID. It has been reported [http://logikir100.tripod.com/Vistron.htm] that a One for all universal remote control set up with code 0435 will work with an MX200i so to use this with a Logik IR100 you would need to do this in a root terminal (login as admin):

Enable write access:

# mount / -orw,remount

Copy the existing config file:

# cp /etc/config/lircd_config825.conf /etc/config/lircd_config1012.conf

Disable write access again:

# mount / -oro,remount

and reboot:

# reboot

And everything should work! No changes are required to the
/root/hwconfig/configXXXX.txt file.

Note that some functions, such as volume control, may need to be enabled in the /root/hwconfig/configXXXX.txt file for the corresponding buttons on the remote to respond correctly but no changes are required for the basic functions.

=== Using any remote control ===

It should be possible to use any remote control using a suitable configuration file. Check http://www.lirc.org/remotes to see if details for your remote control are available or use irrecord, part of lircd available on linux and probably windows, to create a new file.

Note: Not tested with raw codes.

I've used a One for all URC-3920 [http://www.oneforall.com/en_uk/product/1/universal-remotes/2/comfort/153/slim-line-2] programmed for code 02230 to make this lircd_configXXX.conf file:

# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.3(default) on Fri Nov 5 13:52:36 2010
#
# contributed by GC
#
# brand: One for All - urc3920 Code:02230
# model no. of remote control:
# devices being controlled by this remote:
#
begin remote
name urc3920-02230
bits 13
flags RC5|CONST_LENGTH
eps 30
aeps 100
one 866 909
zero 866 909
plead 858
gap 113721
toggle_bit 2
begin codes
# button: menu
v 0x1135
# button: power
O 0x1101
# button: 1
C 0x111E
# button: 2
D 0x111F
# button: 3
E 0x1120
# button: 4
F 0x1122
# button: 5
G 0x1123
# button: 6
H 0x1124
# button: 7
I 0x1126
# button: 8
J 0x1127
# button: 9
K 0x1128
# button: ./..
k 0x1130
# button: 0
L 0x112B
# button: av
i 0x112F
# button: vol+
U 0x1116
# button: vol-
V 0x111A
# button: mute
W 0x1117
# button: ok
R 0x1111
# button: ch+
A 0x1119
# button: ch-
B 0x111D
# button: up
p 0x110E
# button: down
q 0x1114
# button: left
N 0x1110
# button: right
R 0x1112
# button: red
c 0x1132
# button: green
## 0x1129
# button: yellow
e 0x1125
# button: blue
f 0x111C
# button: rew
Z 0x1105
# button: ff
Y 0x1108
# button: pause
t 0x112E
# button: play
s 0x112E
# button: rec
## 0x110C
# button: stop
b 0x110B
# button: guide
d 0x1113
# button: info
3 0x110F
# button: exit
N 0x111B
end codes
end remote

The top of the file describes the characteristics of the remote - timings etc. The codes section translates a remote control code (eg. 0x1135) into a single character that the radio decodes as a button (v).

This has the advantage over the MX200i universal remote method of the buttons being directly set to the required function, no keymapping is required. The descriptions in between the codes above are the actual buttons on the remote, not Reciva's name. It's easy to change.

Note that the version of lircd in the Reciva software doesn't seem to understand the toggle_bit_mask command so this may need to be changed to the equivalent toggle_bit command (toggle_bit_mask 0x0 will become toggle_bit 0 and for RC5 codes, as above, 0x800 will become 2).

The list of available options is:

lirc code to event mapping table from idrv_input_event.c (!)
'A' = INPUT_UP
'B' = INPUT_DOWN
'C' = INPUT_PRESET_1
'D' = INPUT_PRESET_2
'E' = INPUT_PRESET_3
'F' = INPUT_PRESET_4
'G' = INPUT_PRESET_5
'H' = INPUT_PRESET_6
'I' = INPUT_PRESET_7
'J' = INPUT_PRESET_8
'K' = INPUT_PRESET_9
'L' = INPUT_PRESET_10
'M' = INPUT_REPLY
'N' = INPUT_BACK
'O' = INPUT_POWER
'P' = INPUT_POWER_ON
'Q' = INPUT_POWER_OFF
'R' = INPUT_SELECT
'S' = INPUT_RELEASE
'T' = INPUT_SHIFT
'U' = INPUT_VOL_UP
'V' = INPUT_VOL_DOWN
'W' = INPUT_MUTE
'X' = INPUT_ZOOM
'Y' = INPUT_SKIP_NEXT
'Z' = INPUT_SKIP_PREVIOUS
'a' = INPUT_PLAY_PAUSE
'b' = INPUT_STOP
'c' = INPUT_PLAYBACK_MODE
'd' = INPUT_BROWSE_QUEUE
'e' = INPUT_ALARM
'f' = INPUT_SLEEP_TIMER
'g' = INPUT_AUDIO_SOURCE
'h' = INPUT_SNOOZE
'i' = INPUT_STORE_PRESET
'j' = INPUT_RECALL_PRESET
'k' = INPUT_EXTEND_PRESET "--/-"
'l' = INPUT_AUDIO_SOURCE // XXX for backwards compatibility
'm' = INPUT_SWITCH_MODE_TO_IRADIO
'n' = INPUT_SWITCH_MODE_TO_MEDIA_PLAYER
'o' = INPUT_SWITCH_MODE_TO_LINE_IN
'p' = INPUT_RC_UP
'q' = INPUT_RC_DOWN
'r' = INPUT_FM_STEREO_MONO_SWITCH
's' = INPUT_PLAY
't' = INPUT_PAUSE
'u' = INPUT_PRESET_MENU
'v' = INPUT_CONFIGURE_MENU
'w' = INPUT_SWITCH_MODE_TO_FM
'x' = INPUT_SEEK_DOWN
'y' = INPUT_SEEK_UP
'0' = INPUT_REPEAT
# // don't use '1', it's reserved for unused keys
'2' = INPUT_FORWARD
'3' = INPUT_INFO
'4' = INPUT_EQ
'5' = INPUT_MENU_TOP

If anyone would like to copy all the lircd config files from /etc/config/ give them the corresponding radio names and send them to <lirc@bartelmus.de> it would give anyone missing a remote control the chance to use their radios without having to install Sharpfin. These files describe all the signals required to controll all the radios factory fitted with an IR sensor.

=== Diagnosing problems ===

If the remote control doesn't work at all then restart lircd from the command line and see what it outputs. To restart it is first necessary to stop any running instance of lircd.

Find the process number using:
# ps -A | grep lirc

This should give an output something like:

102 root 1464 S < /usr/sbin/lircd -d /dev/lirc/0 /etc/config/lircd_conf
133 root 2280 S grep lirc

If nothing is returned lircd isn't running. In this case the number we need is 102, so use:

# kill -9 102

and then simply:

# lircd

and see what errors are shown, hopefully they're meaningful.

Tested on Logik IR200 & BT radio.

----

sources:

[http://groups.google.co.uk/group/sharpfin/browse_thread/thread/1b78b9adefcd8067 Google groups thread on this]<br/>
[http://logikir100.tripod.com/Logik.htm Logic]<br/>
[https://www.sharpfin.org/index.php?title=Config.txt_File Config.txt]<br/>
<br/>
How to add remote control function to a BT radio:

[http://logikir100.tripod.com/irmod.htm IRmod]<br/>

Enabling Login

2025-06-08T12:41:05Z

Philipp:

<table border=0>
<tr>
<td>
== Introduction ==

Keep [[Up-To-Date]] by e-mail with Sharpfin updates and releases.

'''Enabling Login is provided for developers and programmers. It enables alternative software to be developed for the radio.'''

In order to enable logins on the radio, it is necessary to apply a patch.
To do this, you will need the following:

* A PC running Windows or Linux
* For Windows PCs, you will need to install Cygwin
* The Patch Server
* A Patch File
</td>
<td>
[[Image:Patch.jpg]]
</td>
</tr>
</table>

== Warning ==

Please read this: [[10 Sure-Fire Ways to Trash Your Radio]]

Patching your radio involved writing to part of the flash memory which is normally read-only. Patching involved running scripts we have developed and tested on only a small number of radios.

By patching the radio, you acknowledge that we cannot be held responsible for any losses incurred should the patching fail, you render the radio useless or you lock yourself out of your radio.

Please be aware that the only known method of recovery is the use of JTAG, and that route has not been rigorously developed and tested by ourselves.

== Video Guides ==

If you want a very basic introduction, see the diagrams on the [[Changing Your Radio]] page.

* Sharpfin Video Guide to Patching the Reciva Radio: [http://www.youtube.com/watch?v=WsRVQp1Ug7A Part 1 - Setup]
* Sharpfin Video Guide to Patching the Reciva Radio: [http://www.youtube.com/watch?v=QQN5oDGFcBE Part 2 - Patching]
* Sharpfin Video Guide to Patching the Reciva Radio: [http://www.youtube.com/watch?v=kocuTj7RuDk Part 3 - Post-Patch]

== Patch Files ==

* [https://www.sharpfin.org/images/7/7b/PatchingTheRecivaRadio.pdf PatchingTheRecivaRadio.pdf]
* Download the patchserver and patchfiles from the [[Releases]] page

'''Do NOT install the patchserver into a directory containing spaces. With Windows XP, the desktop is in a subdirectory which contains spaces, unlike the video example which was run on Vista'''

''NOTE: There are two different ways of driving the LCD, and our program only caters for one of them at the moment. If you don't see anything on the screen when running the test, it is highly likely that you have the 'other one'. You can still patch the radio, but will get no indication on the screen of what is going on, so take care. We are working on updating our libreciva library to accomodate the other mechanism, and need testers, so please volenteer if you can spare the time''

''NOTE: We recommend uninstalling any previous third party patches (e.g. ssh) before applying these patches, due to the memory and disk requirements of the radio''

'''IMPORTANT XP please read:''' The directory paths for both Patchserver and Patchfiles must have NO spaces. It would appear wise to also install cgywin in a directory without spaces. All seem to have fewer problems if installed on C:\ rather than any other drive label. In addition, whilst the Windows Firewall may have "allowed" the applications, it can cause issues, so one might consider turning off the Firewall for the duration of a patching operation.

== Once Installed ==

Once you have enabled login, you will find that a webserver and a login server are running. With these, you can:

* Look at the radio configuration
* Run your own scripts and programmes
* Enable new features on the radio, such as alarms see [[Config.txt_File]]
* Download a Reciva firmware upgrade patchfile. Please Read [[Changing Firmware]] before attempting to do so

----

History of installations and related notes below this line

== Installed ==

The login has been enabled on a number of radios ... here is a snapshot of the feedback. If you want to ask questions of other radio users, please use the groups via the [[Up-To-Date]] page:

* 11 January 2009, Strong SRT1000W
* 06 September 2008, Ipdio Style
* 23 September 2007, Logik IR100, SC, 0.2
* 24 September 2007, Logik IR100, Some issues with getting the file to run as Windows/Vista renaming things a bit, and confusion over 01 and 01b file names ... see discussion on the Reciva forums., TS, 0.3
* 24 September 2007, IPDIO, Great work!, PP, 0.3
* 28 September 2007, Logik IRMA1, SC, 0.3
* 28 September 2007, Logik IR100, Couldn't get the patchserver to work in windows vista but linux worked ok ), ST, 0.3
* 6 October 2007, Tevion 5404, The LCD text did NOT show during update, SJ, 0.3
* 10 October 2007, Logik IR100, Additional... I installed the base package first followed by the www_0.4. The web page installed at www-0.4 has a broken link to this form. (i found it using telnet :-) ). I also nothiced that the radio likes to be properly power cycled after changing the network parameters. Otherwise I have had it go mute and be reluctant to get out over the net. As soon as I powercycled it, everything is fine. I'd just like to say I think you're doing a brilliant job here. I really appreciate the work you guys have done. (I also love the idea of telnetting to my radio :-) ) Cheers. AY, AY, 0.4
* 11 October 2007, Logik IR100, TM, 0.4
* 11 October 2007, Logik IR100, TM, 0.4
* 15 October 2007, Logik IR100, I used the linux patchserver programme. For some reason the reciva station scan always timed out through the patchserver. The lookups were working, just happening too slowly. However I tried the test-patch which worked, so I went with the base patch and that worked fine too. Now I'm going to start screwing up my courage to go for a firmware upgrade. Many thanks for all your work., NS, 0.4
* 16 October 2007, Logik IR100, LJ, 0.4
* 16 October 2007, Logik IR100, Everything worked OK! :-) Thank you for the all the hard work! Looking forward to see some new stuff. Keep up the good work!, GX, 0.4
* 16 October 2007, Logik IR100, AN, 0.4
* 19 October 2007, Logik IR100, Now to add the webserver base and try an upgrade..., PK, 0.4
* 20 October 2007, Magicbox Imp Adapt, Didnt get the message for the test patch, and to telnet in from my linux box, telnet -K <ipadd> needs to be run to avoid automatic encryption negotiation, SC, 0.4
* 20 October 2007, Logik IR100, Just to let you know the Web server pages do not apear to work coprectly in Firefox (you dont get the menu's on the left) but are fine in internet explorer. Top job keep up the good work. :), PS, 0.4
* 20 October 2007, Logik IR100, AN, 0.4
* 22 October 2007, Logik IR100, (also complete new firmware to fix upnp), JR, 0.4
* 22 October 2007, Logik IR100, AN, 0.4
* 22 October 2007, Logik IR100, Lol. Thanx duderz. Looking forward to whatever you can do with the Barracuda. Cheerz., TM, 0.5
* 28 October 2007, Logik IR100, The patch installed successfully, thank you. Very useful piece of work! Again, many thanks!, PI, 0.5
* 1 November 2007, Logik IR100, Congrats on all the hard work - very impressive. Many thanks, FR, FR, 0.5
* 8 November 2007, Logik IR100, SM, 0.5
* 12 November 2007, Logik IR100, Installed latest IPDio software on IR100 - seems to be ok and I now have a wifi signal meter. IP address entering method has changed from menu 'pick and choose' selection method to changing default value of 0 for each number by using knob rotation instead, JN, 0.5
* 16 November 2007, Logik IR100, AN, 0.5
* 17 November 2007, Logik IR100, Could you create a sample-file for that function ? ->add alarm ..
* 30 January 2008, Tangent Quatro, Linux patch sever 0.5, patchfile 0.3
https://www.sharpfin.org/images/1/14/LCD-menu.jpg, TM, 0.5
* 6 Feb 2008, Tangent Quattro, Put on Server and basepatch, the 257-a-421-a-041 service pack on the Quattro allowed totally unhindered editing of the config989.txt file to make menu's much more friendly. (M0AUR)
* 8 Feb 2008, Argon iNet 1, to edit config935.TXT (stations-history, history-size, force-metadata) and all_radios.txt (reply-button-function). Works fine. These options not localised in Danish language though.
* 7 Aug 2008, Bush TR2015

== Thanks ==

Special thanks must go to rdk for his help in getting us going with this process !!!

MediaWiki:Common.css

2025-06-08T12:38:30Z

Philipp:

/* CSS placed here will be applied to all skins */

.footer_image {
margin-top:9px;
width:100%;
height:178px;
text-align:center;
background-image:url(/images/5/53/Sharpfin_water.png)
}

.note {
background-position: left 7px top 50%;
padding: 0.5em 0.5em 0.5em 40px;
margin: 0.5em 0;
overflow: hidden;
background-color: #f8f9fa;
color: #333;
background-repeat: no-repeat;
border: 1px solid #ddd;
}
.note-inline {
display: inline-block;
vertical-align: middle;
}
.note-info {
background-color: #eaf3ff;
color: #333;
/* [[File:OOjs_UI_icon_information-progressive.svg]] */
background-image: url(https://upload.wikimedia.org/wikipedia/commons/e/ec/OOjs_UI_icon_information-progressive.svg);
background-size: 25px;
border-color: #a3caff;
padding-left: 40px;
min-height: 25px;
}
.note-reminder {
background-color: #fff9ea;
color: #333;
/* [[File:OOjs_UI_icon_lightbulb-yellow.svg]] */
background-image: url(https://upload.wikimedia.org/wikipedia/commons/a/a8/OOjs_UI_icon_lightbulb-yellow.svg);
background-size: 25px;
border-color: #fc3;
min-height: 25px;
}
.note-warn {
background-color: #fff9ea;
color: #333;
/* [[File:OOjs_UI_icon_alert-warning.svg]] */
background-image: url(https://upload.wikimedia.org/wikipedia/commons/3/3b/OOjs_UI_icon_alert-warning.svg);
background-size: 25px;
border-color: #fc3;
min-height: 25px;
}

.note-error {
background-color: #fee7e6;
color: #333;
/* [[File:OOjs_UI_icon_notice-destructive.svg]] */
background-image: url(https://upload.wikimedia.org/wikipedia/commons/b/bf/OOjs_UI_icon_notice-destructive.svg);
background-size: 25px;
border-color: #c33;
min-height: 25px;
}

@media screen {
html.skin-theme-clientpref-night .note {
background-color: transparent;
color: inherit;
}
}

@media screen and (prefers-color-scheme: dark) {
/* automatic mode */
html.skin-theme-clientpref-os .note {
background-color: transparent;
color: inherit;
}
}

Wishlist

2025-06-08T12:36:40Z

Philipp: Created page with "= Alternative firmware wishlist = The following list shows some features which would be possible to implement with the new firmware. This list is not complete, neither definitive, feel free to add your own ideas. * Show the time of day while playing audio * Running the radio without depending on the Reciva databases * Support for additional audio codecs (ogg, flac, aacp etc) and network protocols * New Feature : play stations that use flash embedded players * Bett..."

= Alternative firmware wishlist =

The following list shows some features which would be possible to implement with the new firmware. This list is not complete, neither definitive, feel free to add your own ideas.

* Show the time of day while playing audio

* Running the radio without depending on the Reciva databases

* Support for additional audio codecs (ogg, flac, aacp etc) and network protocols

* New Feature : play stations that use flash embedded players

* Better control over audio: equalizer, panning, etc.

* The Barracuda provides an USB 1.1 Host interface - playing from USB storage device ?

* Accessibility features, e.g. talking menus for the blind

* Improvement : Direct access to Alarm and Sleep time settings form keyboard.

* Improvement : Stable access to Windows share folders, even if the number of files is huge !

* Improvement : Stable implementation of UPnP .

* New Feature : Offer the ability to display as a "ticker" the headlines of an RSS flux.

* New Feature : Embedded webserver to modify the configuration of the radio.

* New Feature : Checking periodically a pop3 account and display the number of unread mail.

* Improvement : "my podcast" feature: Possibility to enqueue in the playlist all the files in a podcast.

* Improvement : Wake up to a radio program.

* Improvement : Offer the ability to pause a podcast.

* ... More here ...

* Why not support for radiotime.com? Free for open source projects http://developer.radiotime.com

* New feature : Support server side plug-ins on web server - e.g. PHP

* Improvement : Clock on Display when playing.

* Improvement : Enable Back button to access the sleep timer control from the playing screen.

* Improvement : Option to get rid of that Damn infantile 'Real Enabled' banner. - Replace with a clock display?

* Improvement : Option to choose the wake to any station from 'My Stations' rather than JUST the presets.

* New Feature : Support for LastFM and Pandora from non US locations

* New Feature : Add usb memory stick and input station, stream & podcast addresses through the Sharkfin interface.

* New Feature : An option to import My Stations/streams/podcasts etc from Reciva to safe storage on the device.

* New Feature : A means of patching the config files through a more user friendly frontend integrated into the Sharkfin browser would be a real leap forward for many - vi is a real headbanger for us not so techy folk! Even being able to use vi from within the browser would be a leap forward.

* New Feature : Is it possible or practical that a radio button type frontend could be used to create and execute a script on the radio? I am pretty sure that some firmwares write to the config files when they update.

* New Feature : At the moment, the scroll control on an IR100 is 'dead' while a station is playing. This is a waste, it would be better if it did something (anything). I suggest that scrolling through the stations in My Stuff would be very handy, and indeed is intuitively what it "should" do.
** I agree with this, as has already been tried, it is supposed to be a volume control, it is beyond me why so many manufacturers prefer the two knob design, as one would presumably cut costs.
** I would say that the only intuitive thing for this to do would be to rotate through either history or my stations as you suggest, and maybe a mode for adjusting a sleep function when an alarm sounds, turn to the required time and press to set.
** Firmware v257-a-756-a-186 allows to use the scroll button to browse through the internet stations. (Currently no source available for this version! Has this been fixed for the IR100, too?) --[[User:Hp|Hp]] 13:01, 3 January 2009 (CET)

* Improvement : "snooze" button as a copy of the "back" button (OKANO TR 2608i / Sanyo R227) --[[User:Hp|Hp]] 13:01, 3 January 2009 (CET)

* Improvement : instead of "shift" to select station presets 5-8, use multiple keypresses (seen on Roku SoundBridge) --[[User:Hp|Hp]] 13:01, 3 January 2009 (CET)

* Improvement : more station presets (e.g. 16 instead of 8), selected using multiple keypresses --[[User:Hp|Hp]] 13:01, 3 January 2009 (CET)

Watchdog

2025-06-08T12:36:07Z

Philipp: Created page with "== Overview == The Libreciva dog function provides control of the processor's watchdog timer. In order to use the library function, you must include the header file: <syntaxhighlight> #include "dog.h" </syntaxhighlight> === int dog_init() and void dog_exit() === These functions are used to initialise and shut down the watchdog system. dog_init() returns true on success, or false if there was an error accessing the hardware. Note that dog_exit() simply leaves..."

== Overview ==

The [[Libreciva]] dog function provides control of the processor's watchdog timer.

In order to use the library function, you must include the header file:

<syntaxhighlight>
#include "dog.h"
</syntaxhighlight>

=== int dog_init() and void dog_exit() ===

These functions are used to initialise and shut down the watchdog system. dog_init() returns true on success, or false if there was an error accessing the hardware.

Note that dog_exit() simply leaves the watchdog in whatever state it has been set - if you want the dog disabled, you must call dog_disable() before calling dog_exit().

=== int dog_enable() and int dog_disable() ===

These functions are used to enable and disable the watchdog. the functions return 0 on success, or -1 if there is an error accessing the hardware.

=== int dog_isenabled() ===

This function reports the current enable (true) or disable (false) state of the watchdog. Note that this function simply reports which dog_enable() / dog_disable() function was last called from this application. It is not possible to read the enabled status back from the hardware.

=== int dog_kick() ===

This function is used to kick the dog. It returns 0 on success, or -1 if there has been a problem accessing the hardware.

Up-To-Date

2025-06-08T12:35:30Z

Philipp: Created page with "== Let's Get Talking == We have also created an interactive mailing list which you can use to communicate with fellow Reciva internals enthusiasts on [http://groups.google.co.uk/group/sharpfin sharpfin on Google Groups]. We encourage you to share discoveries and problems, code and patches, however .... We still encourage (and need) you to carry on editing, updating and maintaining this website, as it is the definitive resource for the project."

== Let's Get Talking ==

We have also created an interactive mailing list which you can use to communicate with fellow Reciva internals enthusiasts on [http://groups.google.co.uk/group/sharpfin sharpfin on Google Groups]. We encourage you to share discoveries and problems, code and patches, however ....

We still encourage (and need) you to carry on editing, updating and maintaining this website, as it is the definitive resource for the project.

File:Wiggler2.png

2025-06-08T12:33:46Z

Philipp:

File:SharpflashPinBoardOn.jpg

2025-06-08T12:33:26Z

Philipp:

File:SharpflashPinBoardOff.jpg

2025-06-08T12:33:03Z

Philipp:

File:SharpflashWigglerBackside.jpg

2025-06-08T12:32:45Z

Philipp:

File:SharpflashCableExample.jpg

2025-06-08T12:32:26Z

Philipp:

Unbricking

2025-06-08T12:32:01Z

Philipp:

== Introduction ==

If your radio bricked after you edited the config file, it is possible to unbrick it by removing the Barracuda module and placing it in a radio that has a different hardware-id e.g. a module from an Intempo (761), inside a Logik IR100 (1012). Once powered up, you can login and restore the config file edits (since the new radio boots using the config files for its radio hardware-id, not the one you messed up).

The following procedure will take you through the restoration of your radio using a simple JTAG cable, with software we have provided.

== Prerequisites ==

In order to recover a bricked radio, you will need:

* JTAG hardware
* Software for flashing over JTAG
* An image to flash to the radio (see [[Making a backup]])
* A lot of patience

== JTAG hardware ==

'Wiggler' compatible cables are a popular low-cost cable, and well supported by the free jtag tools. Plans to make your own are widely available, and prebuilt ones can be found cheaply on ebay and similar sites.

A "universal" wiggler will come with bare wires which can be soldered to the [[Media:Barracuda-board-outline.jpg|jtag test points]] on the barracuda board.

<table border=0><tr><td>
[[Image:Wiggle.png|Wiggler Schematic]]
</td><td>
[[Image:Jtag-soldering.jpg]]
</td></tr></table>

'''N.B. The Barracuda board needs to be installed in a powered up radio (standby is OK) for the JTAG process to work.'''

Sharpflash supports only wigglers connected on the '''Parallel ports''' (LPT1, LPT2, LPT3) of your computer. Since these ports become very rare there may be the need to update Sarpflash to support wigglers on USB ports etc.

A cable and the JTAG unit that worked in a backup/restore test were:
<table border=0><tr><td>
[[Image:SharpfinWigglerExample.jpg|200px]]
</td><td>
[[Image:SharpflashCableExample.jpg|500px]]
</td></tr></table>
Note that the cable for this JTAG unit has both a male end (to be attached to the PC) and a female end that will be directly connected to the JTAG unit. The cable should NOT be too long (max 5m) and it should be a "normal" printer cable (DB-25), but '''not''' with 36 pins on the female end (like some very '''old''' printers had/have), but with the D-Sub (because it is D-shaped) 25pin on both sites (D-Sub M/F 25pin).

The off-the-shelf unit should have the necessary bare wires to solder to the Reciva board. The only problem with those commercial wigglers is their usage of input pins. Hence, it may be necessary to adjust some of the inputs, e.g:

[[Image:SharpflashWigglerBackside.jpg|200px]]

=== Soldering ===
The bare cables of the JTAG unit must be soldered directly to the Reciva board on the JTAG interface.
It seems that only Ground (GND) and the power supply (VCC) are available as pins on the board, for the rest we need to solder the bare cables directly to the gold-plated contact points.

We need at least 4 of those (excluding also the nTrst point, that was not always needed in our tests).
Hint: Put very little solder on the points of the Reciva board first, then a little bit on the bare wire and then connect them using a solder iron. This should not be too difficult and you do not need special soldering skills, just be sure to not damage the gold-plated contact points. An alternative that worked too is to build a transparent board (plastic, plexi) where you can plug in you bares, that you will place just above the Reciva board:
<table border=0><tr><td>
[[Image:SharpflashPinBoardOff.jpg|200px]]
</td><td>
[[Image:SharpflashPinBoardOn.jpg|500px]]
</td></tr></table>
But note that to construct the transparent board and fix the cables such that they are perfectly connected to the Reciva board may be even more difficult than solder the 4 + 2 wires to the board.

Or see [http://recivarefuge.net/sharpfin/Barracuda%20connector.pdf Barracuda JTAG Connector]for instructions to make a custom connector which does not require soldering to the gold pads on the Reciva module.

10/10/12 : [[User:Philipp]] used a off-the-shelf wiggler based on [[Media:wiggler2.png|this]] circuit that needed small modification (and soldering skills), see images above

19/08/08 : I used a wiggler based on [[Media:wiggler2.png|this]] circuit. This worked 100% on the first attempt. Note this uses HC rather than AC logic, which is advised in several places.

== JTAG Flashing Software ==

The application sjf2410, along with the error correction code from the linux kernel have been modified to produce a bespoke utility for the baracuda module's NAND flash. It uses the wiggler cable in the parallel port.

* [https://www.sharpfin.org/images/a/a4/Sharpflash_v0.4.zip Sharpflash v 0.4] - Source Code* ('''OLD:''' [https://www.sharpfin.org/images/c/c1/Sharpflash-src-0.1.tar.bz2 Sharpflash v 0.1 Alpha])
* [[Sharpflash Bugs]]

 * Sharpflash will be only provided as a source code snapshot (from github) since it is for more advanced users only which should be able to make/build the utility and adapt it

=== Requirements ===
* Hardware
** A parallel DB-25 female port
** Reciva board (and the radio itself, we need to plug the board into the Radio's main board too to be able to run Sharpflash, after soldering the bare wires of the wiggler)
** Cable (depending on your JTAG unit, LPT cable, DB-25 M/F 25 pin)
** Solder iron
* Software
** Linux with root account OR Win 32bit w/ Cygwin and giveio.sys<sup>[[#foot_giveio|giveio]]</sup> installed (we could think of supporting also Inpout32.dll<sup>[[#foot_inpout32dll|inpout32]]</sup>)
** Newest version of Sharpflash

Sharpflash v 0.4 was successfully tested under Windows (Cygwin with ioperm and giveio) and under Ubuntu Linux (both running in a 32 bit environment).
To use Sharpflash with a 64bit version of windows we may need Inpoutx64.dll<sup>[[#foot_inpoutx64dll|inpout64]]</sup>.

This version of sharpflash supports reading and writing of the NAND flash using the wiggler parallel port interface.

'''This software is far from perfect. It takes a lot of time to restore/backup the whole NAND flash'''

=== Sharpflash Options ===

$ ./sharpflash.exe -h

Sharpfin Flash Programmer. https://www.sharpfin.org/

sharpflash [-p 1|2|3] [-r|-w filename start length ]
sharpflash [-p 1|2|3] [-b]

-r -w Read flash to file, or write file to flash
-b Check flash for bad blocks
-p <n> n = 1, 2 or 3. Use LPT1 (default) LPT2 or LPT3 parallel port
filename Destination / source filename, the file must be in nanddump format
start Hex start address in NAND for read/write, must be a multiple of 0x4000
length Hex length to read/write. if file is too short,
NAND will be filled with 0xFF. Must be a multiple of 0x4000

If no r,w or b argument is supplied, the program just tries to read the
JTAG device ID of the flash and CPU using the configured parallel port,

For r,w and b commands, the output data contains:

w - page written OK
r - page read OK
. - page check OK
b - page/block identified as bad
B - page/block has just been marked bad

v0.4, https://www.sharpfin.org/

=== Reading Flash Images ===

You can make a back-up of your flash via JTAG using the following format commands:

sharpflash -r kernel-mtd.bin 004000 0fc000

Will extract the contents of the kernel partition into 'kernel-mtd1.bin', which is a ''nanddump'' format file, skipping any bad sectors as it goes. Have a look at [[Reciva NAND Flash]] for the background on the flash structure.

Sharpfin Flash Programmer - https://www.sharpfin.org/
.
Found S3C2410 processor on JTAG Cable
Found K9F2808UOC on processor
Reading NAND Flash:
destination = kernel-mtd1.bin
start addr = 0x4000
length = 0xFC000
.
Address Progress Remaining
------- -------------------------------- ---------
0004000 rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr 9h 12m
0008000 rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr 9h 11m
000C000 rrrrrr

=== Getting Bad Block Information ===

This is not needed for programming, however it is recommended that you keep a record of the bad blocks marked by the manufacturer as bad, because this information is stored in re-programmable memory, and it may be useful to be able to distinguish between manufacturer-defined bad blocks, and user-defined bad blocks.

sharpflash -b

The program will output several lines, with each '.' representing a 16K block which is marked as good, and a 'b' for each block which is marked bad.

Sharpfin Flash Programmer - https://www.sharpfin.org/
.
Found S3C2410 processor on JTAG Cable
Found K9F2808UOC on processor
Checking NAND Blocks
0000000: ................................................................
0100000: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb...............

=== Writing Flash Images ===

This process takes a long time to run - roughly 80 seconds per 16KBytes, so a full 16Mb flash will take about 24 hours.

'''When you are choosing your images to write, make sure that they are in 'nanddump' format. Writing images to flash that are ''not'' in 'nanddump' format will result in valid blocks being marked bad'''

sharpflash -w boot-mtd.bin 000000 04000

Will write the boot sector from the file boot-mtd.bin, and will produce an output similar to this:

Sharpfin Flash Programmer - https://www.sharpfin.org/
.
Found S3C2410 processor on JTAG Cable
Found K9F2808UOC on processor
Writing NAND Flash:
source = boot-mtd.bin
start addr = 0x0
length = 0x04000
.
Address Progress Remaining
------- -------------------------------- ---------
0000000 wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww 0h 00m

If you want to restore your whole radio nandumps, you may need all of the following commands:
sudo ./sharpfin -w boot-mtd.bin 000000 004000
sudo ./sharpfin -w kernel-mtd.bin 004000 0FC000
sudo ./sharpfin -w root-mtd.bin 100000 D00000
sudo ./sharpfin -w config-mtd.bin E00000 100000
sudo ./sharpfin -w debug-mtd.bin F00000 100000

As above, the first number is the starting address and the second the nandump size (in hex).
Please double-check if these sizes/addresses are correct for your radio too (e.g. via a working sharpfin webserver backup page or just try to get the numbers from the file-size and calculate the "next" address respectively).
The formula of course is:
new address = old address + old size
(the order should always be boot, kernel, root, config, debug; but please double-check that too for your radio)

= Interesting Information / Links =

* [http://www.olimex.com/dev/arm-jtag.html Arm Programming Info]
* [http://openocd.berlios.de/ OpenOCD Support for NAND flash via the S3C2410's built in controller]
* [https://lists.berlios.de/pipermail/openocd-development/2007-March/000115.html patch supporting the K9F1208 Flash (similar to the K9F2808)]
* [http://openwince.sourceforge.net/jtag/ OpenWinCE JTAG tools]
* [http://jtager.cvs.sourceforge.net/jtager/jtager/doc/s3c2410.bsdl?view=log s3c2410.bsdl Support for OpenWinCE]
* [http://jtager.sourceforge.net jtager]
* [http://wiki.openmoko.org/wiki/Sjf2410-linux sjf2410 Used by the OpenMoko project]
* [http://www.mizi.com/developer/s3c2410x/ jflash-s3c2410]
* [http://www.freelabs.com/~whitis/electronics/jtag/ JTAG Information]
* [http://www.ens-lyon.fr/LIP/Pub/Rapports/RR/RR2006/RR2006-08.pdf Arm/Linux Booting method]
* [http://www.bioinspired.com/users/ajg112/electronics/parallelPort.shtml PC Parallel Port Access From Linux]
* [http://www.ixo.de/info/usb_jtag/ JTAG USB Programming Info]
* [http://www.ftdichip.com/Documents/ProgramGuides/FTCJTAGPG13.pdf FTDI Library, used by Altera ByteBlaster]
* <span id="foot_inpoutx64dll">[http://logix4u.net/parallel-port/26-inpoutx64dll-for-win-xp-64-bit Windows IO port access on 64bit environment: inpoutx64.dll]</span>
* <span id="foot_inpout32dll">[http://logix4u.net/component/content/article/14-parallel-port/16-inpout32dll-for-windows-982000ntxp Windows IO port access on 32bit environment: inpout32.dll]</span>
* <span id="foot_giveio">[http://www.cs.ucr.edu/~eblock/pages/pictools/giveio.html Giveio.sys and Library Loader for Windows direct IO port access]</span>

File:SharpfinWigglerExample.jpg

2025-06-08T12:29:22Z

Philipp:

File:Wiggle.png

2025-06-08T12:28:51Z

Philipp:

File:Jtag-soldering.jpg

2025-06-08T12:28:18Z

Philipp:

Unbricking

2025-06-08T12:27:55Z

Philipp: Created page with "== Introduction == If your radio bricked after you edited the config file, it is possible to unbrick it by removing the Barracuda module and placing it in a radio that has a different hardware-id e.g. a module from an Intempo (761), inside a Logik IR100 (1012). Once powered up, you can login and restore the config file edits (since the new radio boots using the config files for its radio hardware-id, not the one you messed up). The following procedure will take you th..."

== Introduction ==

If your radio bricked after you edited the config file, it is possible to unbrick it by removing the Barracuda module and placing it in a radio that has a different hardware-id e.g. a module from an Intempo (761), inside a Logik IR100 (1012). Once powered up, you can login and restore the config file edits (since the new radio boots using the config files for its radio hardware-id, not the one you messed up).

The following procedure will take you through the restoration of your radio using a simple JTAG cable, with software we have provided.

== Prerequisites ==

In order to recover a bricked radio, you will need:

* JTAG hardware
* Software for flashing over JTAG
* An image to flash to the radio (see [[Making a backup]])
* A lot of patience

== JTAG hardware ==

'Wiggler' compatible cables are a popular low-cost cable, and well supported by the free jtag tools. Plans to make your own are widely available, and prebuilt ones can be found cheaply on ebay and similar sites.

A "universal" wiggler will come with bare wires which can be soldered to the [[Media:Barracuda-board-outline.jpg|jtag test points]] on the barracuda board.

<table border=0><tr><td>
[[Image:Wiggle.png|Wiggler Schematic]]
</td><td>
[[Image:Jtag-soldering.jpg]]
</td></tr></table>

'''N.B. The Barracuda board needs to be installed in a powered up radio (standby is OK) for the JTAG process to work.'''

Sharpflash supports only wigglers connected on the '''Parallel ports''' (LPT1, LPT2, LPT3) of your computer. Since these ports become very rare there may be the need to update Sarpflash to support wigglers on USB ports etc.

A cable and the JTAG unit that worked in a backup/restore test were:
<table border=0><tr><td>
[[Image:SharpfinWigglerExample.jpg|200px]]
</td><td>
[[Image:SharpflashCableExample.jpg|500px]]
</td></tr></table>
Note that the cable for this JTAG unit has both a male end (to be attached to the PC) and a female end that will be directly connected to the JTAG unit. The cable should NOT be too long (max 5m) and it should be a "normal" printer cable (DB-25), but '''not''' with 36 pins on the female end (like some very '''old''' printers had/have), but with the D-Sub (because it is D-shaped) 25pin on both sites (D-Sub M/F 25pin).

The off-the-shelf unit should have the necessary bare wires to solder to the Reciva board. The only problem with those commercial wigglers is their usage of input pins. Hence, it may be necessary to adjust some of the inputs, e.g:

[[Image:SharpflashWigglerBackside.jpg|200px]]

=== Soldering ===
The bare cables of the JTAG unit must be soldered directly to the Reciva board on the JTAG interface.
It seems that only Ground (GND) and the power supply (VCC) are available as pins on the board, for the rest we need to solder the bare cables directly to the gold-plated contact points.

We need at least 4 of those (excluding also the nTrst point, that was not always needed in our tests).
Hint: Put very little solder on the points of the Reciva board first, then a little bit on the bare wire and then connect them using a solder iron. This should not be too difficult and you do not need special soldering skills, just be sure to not damage the gold-plated contact points. An alternative that worked too is to build a transparent board (plastic, plexi) where you can plug in you bares, that you will place just above the Reciva board:
<table border=0><tr><td>
[[Image:SharpflashPinBoardOff.jpg|200px]]
</td><td>
[[Image:SharpflashPinBoardOn.jpg|500px]]
</td></tr></table>
But note that to construct the transparent board and fix the cables such that they are perfectly connected to the Reciva board may be even more difficult than solder the 4 + 2 wires to the board.

Or see [http://recivarefuge.net/sharpfin/Barracuda%20connector.pdf Barracuda JTAG Connector]for instructions to make a custom connector which does not require soldering to the gold pads on the Reciva module.

10/10/12 : [[User:Philipp]] used a off-the-shelf wiggler based on [[Media:wiggler2.png|this]] circuit that needed small modification (and soldering skills), see images above

19/08/08 : I used a wiggler based on [[Media:wiggler2.png|this]] circuit. This worked 100% on the first attempt. Note this uses HC rather than AC logic, which is advised in several places.

== JTAG Flashing Software ==

The application sjf2410, along with the error correction code from the linux kernel have been modified to produce a bespoke utility for the baracuda module's NAND flash. It uses the wiggler cable in the parallel port.

* [http://www.sharpfin.org/sharpfin/images/a/a4/Sharpflash_v0.4.zip Sharpflash v 0.4] - Source Code* ('''OLD:''' [http://www.sharpfin.org/sharpfin/images/c/c1/Sharpflash-src-0.1.tar.bz2 Sharpflash v 0.1 Alpha])
* [[Sharpflash Bugs]]

 * Sharpflash will be only provided as a source code snapshot (from github) since it is for more advanced users only which should be able to make/build the utility and adapt it

=== Requirements ===
* Hardware
** A parallel DB-25 female port
** Reciva board (and the radio itself, we need to plug the board into the Radio's main board too to be able to run Sharpflash, after soldering the bare wires of the wiggler)
** Cable (depending on your JTAG unit, LPT cable, DB-25 M/F 25 pin)
** Solder iron
* Software
** Linux with root account OR Win 32bit w/ Cygwin and giveio.sys<sup>[[#foot_giveio|giveio]]</sup> installed (we could think of supporting also Inpout32.dll<sup>[[#foot_inpout32dll|inpout32]]</sup>)
** Newest version of Sharpflash

Sharpflash v 0.4 was successfully tested under Windows (Cygwin with ioperm and giveio) and under Ubuntu Linux (both running in a 32 bit environment).
To use Sharpflash with a 64bit version of windows we may need Inpoutx64.dll<sup>[[#foot_inpoutx64dll|inpout64]]</sup>.

This version of sharpflash supports reading and writing of the NAND flash using the wiggler parallel port interface.

'''This software is far from perfect. It takes a lot of time to restore/backup the whole NAND flash'''

=== Sharpflash Options ===

$ ./sharpflash.exe -h

Sharpfin Flash Programmer. http://www.sharpfin.org/sharpfin/

sharpflash [-p 1|2|3] [-r|-w filename start length ]
sharpflash [-p 1|2|3] [-b]

-r -w Read flash to file, or write file to flash
-b Check flash for bad blocks
-p <n> n = 1, 2 or 3. Use LPT1 (default) LPT2 or LPT3 parallel port
filename Destination / source filename, the file must be in nanddump format
start Hex start address in NAND for read/write, must be a multiple of 0x4000
length Hex length to read/write. if file is too short,
NAND will be filled with 0xFF. Must be a multiple of 0x4000

If no r,w or b argument is supplied, the program just tries to read the
JTAG device ID of the flash and CPU using the configured parallel port,

For r,w and b commands, the output data contains:

w - page written OK
r - page read OK
. - page check OK
b - page/block identified as bad
B - page/block has just been marked bad

v0.4, http://www.sharpfin.org/sharpfin/

=== Reading Flash Images ===

You can make a back-up of your flash via JTAG using the following format commands:

sharpflash -r kernel-mtd.bin 004000 0fc000

Will extract the contents of the kernel partition into 'kernel-mtd1.bin', which is a ''nanddump'' format file, skipping any bad sectors as it goes. Have a look at [[Reciva NAND Flash]] for the background on the flash structure.

Sharpfin Flash Programmer - http://www.sharpfin.org/sharpfin/
.
Found S3C2410 processor on JTAG Cable
Found K9F2808UOC on processor
Reading NAND Flash:
destination = kernel-mtd1.bin
start addr = 0x4000
length = 0xFC000
.
Address Progress Remaining
------- -------------------------------- ---------
0004000 rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr 9h 12m
0008000 rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr 9h 11m
000C000 rrrrrr

=== Getting Bad Block Information ===

This is not needed for programming, however it is recommended that you keep a record of the bad blocks marked by the manufacturer as bad, because this information is stored in re-programmable memory, and it may be useful to be able to distinguish between manufacturer-defined bad blocks, and user-defined bad blocks.

sharpflash -b

The program will output several lines, with each '.' representing a 16K block which is marked as good, and a 'b' for each block which is marked bad.

Sharpfin Flash Programmer - http://www.sharpfin.org/sharpfin/
.
Found S3C2410 processor on JTAG Cable
Found K9F2808UOC on processor
Checking NAND Blocks
0000000: ................................................................
0100000: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb...............

=== Writing Flash Images ===

This process takes a long time to run - roughly 80 seconds per 16KBytes, so a full 16Mb flash will take about 24 hours.

'''When you are choosing your images to write, make sure that they are in 'nanddump' format. Writing images to flash that are ''not'' in 'nanddump' format will result in valid blocks being marked bad'''

sharpflash -w boot-mtd.bin 000000 04000

Will write the boot sector from the file boot-mtd.bin, and will produce an output similar to this:

Sharpfin Flash Programmer - http://www.sharpfin.org/sharpfin/
.
Found S3C2410 processor on JTAG Cable
Found K9F2808UOC on processor
Writing NAND Flash:
source = boot-mtd.bin
start addr = 0x0
length = 0x04000
.
Address Progress Remaining
------- -------------------------------- ---------
0000000 wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww 0h 00m

If you want to restore your whole radio nandumps, you may need all of the following commands:
sudo ./sharpfin -w boot-mtd.bin 000000 004000
sudo ./sharpfin -w kernel-mtd.bin 004000 0FC000
sudo ./sharpfin -w root-mtd.bin 100000 D00000
sudo ./sharpfin -w config-mtd.bin E00000 100000
sudo ./sharpfin -w debug-mtd.bin F00000 100000

As above, the first number is the starting address and the second the nandump size (in hex).
Please double-check if these sizes/addresses are correct for your radio too (e.g. via a working sharpfin webserver backup page or just try to get the numbers from the file-size and calculate the "next" address respectively).
The formula of course is:
new address = old address + old size
(the order should always be boot, kernel, root, config, debug; but please double-check that too for your radio)

= Interesting Information / Links =

* [http://www.olimex.com/dev/arm-jtag.html Arm Programming Info]
* [http://openocd.berlios.de/ OpenOCD Support for NAND flash via the S3C2410's built in controller]
* [https://lists.berlios.de/pipermail/openocd-development/2007-March/000115.html patch supporting the K9F1208 Flash (similar to the K9F2808)]
* [http://openwince.sourceforge.net/jtag/ OpenWinCE JTAG tools]
* [http://jtager.cvs.sourceforge.net/jtager/jtager/doc/s3c2410.bsdl?view=log s3c2410.bsdl Support for OpenWinCE]
* [http://jtager.sourceforge.net jtager]
* [http://wiki.openmoko.org/wiki/Sjf2410-linux sjf2410 Used by the OpenMoko project]
* [http://www.mizi.com/developer/s3c2410x/ jflash-s3c2410]
* [http://www.freelabs.com/~whitis/electronics/jtag/ JTAG Information]
* [http://www.ens-lyon.fr/LIP/Pub/Rapports/RR/RR2006/RR2006-08.pdf Arm/Linux Booting method]
* [http://www.bioinspired.com/users/ajg112/electronics/parallelPort.shtml PC Parallel Port Access From Linux]
* [http://www.ixo.de/info/usb_jtag/ JTAG USB Programming Info]
* [http://www.ftdichip.com/Documents/ProgramGuides/FTCJTAGPG13.pdf FTDI Library, used by Altera ByteBlaster]
* <span id="foot_inpoutx64dll">[http://logix4u.net/parallel-port/26-inpoutx64dll-for-win-xp-64-bit Windows IO port access on 64bit environment: inpoutx64.dll]</span>
* <span id="foot_inpout32dll">[http://logix4u.net/component/content/article/14-parallel-port/16-inpout32dll-for-windows-982000ntxp Windows IO port access on 32bit environment: inpout32.dll]</span>
* <span id="foot_giveio">[http://www.cs.ucr.edu/~eblock/pages/pictools/giveio.html Giveio.sys and Library Loader for Windows direct IO port access]</span>

Toolchain

2025-06-08T12:27:23Z

Philipp: Created page with "== Cheat == If you want to cheat, and want to do your development under Cygwin, you can download a pre-compiled cross-compiler toolchain for the Cygwin environment on the Releases page. == Download Crosstool == Crosstool is a collection of scripts which can help you building a cross compiler toolchain without pain. Get the latest version from [http://kegel.com/crosstool/] == Build the toolchain == Reciva uses two different toolchains to build the radio software...."

== Cheat ==

If you want to cheat, and want to do your development under Cygwin, you can download a pre-compiled cross-compiler toolchain for the Cygwin environment on the [[Releases]] page.

== Download Crosstool ==

Crosstool is a collection of scripts which can help you building a cross compiler toolchain without pain. Get the latest version from [http://kegel.com/crosstool/]

== Build the toolchain ==

Reciva uses two different toolchains to build the radio software. gcc 3.3.4 is used for the kernel, and 4.1.0 is used for the userspace applications.

The following creates the 4.1.0 toolchain in /opt.

*First check that you have ''flex'' and ''bison'' as they are required but the toolchain builder doesn't check for them.
*unpack crosstool into /opt and rename it. (You will probably need to be root to do this):

cd /opt
tar -zxvf crosstool-<version>.tgz
mv crosstool-<version> crosstool

*The crosstool builder won't run if you are root but normal users can't write to /opt so set the permissions on the crosstool directory.

chown -R <normal-user> crosstool

*Log in as a normal user and go to /opt
*choose the right flavour and build

export RESULT_TOP=/opt/crosstool
eval `cat arm9tdmi.dat gcc-4.1.0-glibc-2.3.2.dat` sh all.sh --notest

This might take some time. If all goes well, you'll end up with a fresh cross compiler in /opt/crosstool

Finally check if the development package of libc is installed (otherwise [[Crosscompiling]] will most probably fail afterwards):

sudo apt-get install libc6-dev

== Configure Your Shell ==

The sharpfin build scripts look for 'arm-9tdmi-linux-gnu-gcc' and other cross-compiling programs in the path. If you add the following lines to your .bashrc file, any cross-tools programs you build will automatically be added to your path:

export RESULT_TOP=/opt/crosstool
COMPILERS=`find $RESULT_TOP -type d -name bin|tr '\n' ':'`
export PATH=$PATH:$COMPILERS
alias cc=arm-9tdmi-linux-gnu-gcc

The Universal Remote

2025-06-08T12:26:57Z

Philipp: Created page with "dummy"

dummy

Tevion

2025-06-08T12:26:25Z

Philipp: Created page with "== Inside the Tevion 5404 == === Introduction === The Tevion 5404 appears to be three separate functions combined into a single equipment. These functions are: * Internet Radio (Using the Reciva Barracuda Module) * FM Radio * Alarm You use the power button to toggle between the Internet Radio (IR) and the FM Radio functions. Holding in the power button switches the unit off. You hold down the select button to access the Trebble / Bass / Alarm / Clock / press Reset..."

== Inside the Tevion 5404 ==

=== Introduction ===

The Tevion 5404 appears to be three separate functions combined into a single equipment. These functions are:

* Internet Radio (Using the Reciva Barracuda Module)
* FM Radio
* Alarm

You use the power button to toggle between the Internet Radio (IR) and the FM Radio functions. Holding in the power button switches the unit off.

You hold down the select button to access the Trebble / Bass / Alarm / Clock / press Reset Menu.

=== Tevion Differences ===

This seamless integration of functions leads to a few differences between this and other Reciva based radios:

* Because the alarm is outside of the Internet Radio module, you cannot choose which station to start on, you can just choose buzzer, Internet Radio or FM Radio. The radio goes to the last known station. It is unclear what happens if no internet connection is available and IR is selected.
* Because the clock is outside of the Internet Radio module, there does not appear to be any time synchronisation with the internet.
* It appears that the display access is quite different to other radios. It is likely that this model uses I2C to access the display, and this bus is shared between the three functions. This means that the libreciva lcd library is not compatible with the radio (yet!). This can be seen when upgrading the firmware (even the Reciva official upgrades), when the display does not indicate progress.

Source Files

2025-06-08T12:25:53Z

Philipp: Created page with "== Source Files == This page contains the source files, which are used to generate the images and pictures on the Sharpfin Project."

== Source Files ==

This page contains the source files, which are used to generate the images and pictures on the Sharpfin Project.

Software

2025-06-08T12:25:02Z

Philipp:

This page only discusses the non-proprietary software running on the Barracuda module. We do *not* discuss or reverse engineer the 'Reciva Radio Application'.

= Using JTAG To Install an SSH Shell =

The project purpose is to provide an alternative open source solution to the Reciva proprietary software. In order to do this, access to the radio is needed. The following description details how this is achieved using JTAG to dump and restore a modified root image.

[[Software SSH Shell Activation]]

= GPL Firmware =

The reciva radio uses a distribution of Linux for the kernel / core, which is available from [http://www.reciva.com/gpl The Reciva Server]. Interestingly, there are several different releases that contain identically marked (and sized) tarfiles !

Several versions are available, and are summarised in the following table:

= Bootloader =

The good bootloader, found on the Riscstation is the [http://www.simtec.co.uk/products/SWABLE/ ABLE Bootloader], it is possible that this is the loader which is used on the radio module. This is the bootloader shipped with 'bast' platform Samsung 2410 Evaluation Board. The ABLE bootloader is proprietary software from Simtec Electronics. An open source project would have to replace this software with another bootloader such as Das U-Boot.

= Bootloader Information Resources =

* [http://www.aleph1.co.uk/book/print/310 ARM Bootloaders]

= Operating system and device drivers =
The Barracuda module runs [http://familiar.handhelds.org/ Familiar Linux]. Familiar Linux is a derivative of Debian Linux. Debian Linux has been [http://www.debian.org/ports/arm/ ported to several ARM platforms, including bast ]. The reference platform for bast is the [http://www.simtec.co.uk/products/EB2410ITX/spec.html Simtec Electronics EB2410ITX Evaluation Board].

Linux 2.4.26 is running on the ARM CPU within the Samsung device. Sourcecode for drivers for the following devices is acknowledge to be available :

* USB Host device
* PCM audio output
* UART
* 'BAST' real time clock
* I2C interface (what's on the bus?)
* IRDA driver for 'NSC PC87108/PC87338' (is this onboard?)
* LCD (tm13264cbcg / mg1203d / ...)

There is no network interface available onboard, a USB network adapter is used.

It seems that Reciva used the [http://www.debian.org/releases/stable/arm/ch02s01.html.en 'bast' ARM architecture] as a base for their own development.

"Bast is a modern ARM 920 board with a 266MHz Samsung processor. It has integrated IDE, USB, Serial, Parallel,
audio, video, flash and two ethernet ports. This system has a good bootloader which is also found on the CATS
and RiscStation systems."

(bast, cats, and riscstation are evaluation boards by Simtec Electronics)

Additional information about Linux on the 'bast' platform can be found [http://armlinux.simtec.co.uk/index.html here].

= System libraries + utilities =

The following libraries and applications will be needed at least for implementing radio software:

* C-library (glibc/uclibc?)
* Flash write/erase tools: mtd-utils
* Shell + basic unix tools (busybox!)
* codec libraries (libmad, libogg, libvorbis, libflac, etc)
* Support for WLAN and security: wireless tools and wpa_supplicant
* networking libraries for HTTP, RTP, RTSP, MMS, etc
* Webserver (boa?)
* Preferably a scripting language for rapid development and CGI scripts. Lua, perl, ruby ?

= 'Radio' application =

On top of all this, the 'radio application' will be running. This application might consist of various
processes, daemons, CGI-scripts, etc.

The main functions will be

* Handling of the user interface: LCD, buttons and led's
* Configuration of the device using a web server
* Network streaming + audio decoding. VLC for a quick start ?
* ...

== GPIO ==

The software source refers to the various GPIO signals: [[GPIOSignals]]

== I<sup>2</sup>C ==

GPIO provides sets of pins where the board can act as both an I2C master and a slave. Reciva say that [http://corporate.reciva.com/download_files/L1_06_SlaveModeOperation.pdf the module can be controlled over I2C] in slave mode, instead of a directly connected display and keyboard.

Software

2025-06-08T12:24:38Z

Philipp: Created page with "This page only discusses the non-proprietary software running on the Barracuda module. We do *not* discuss or reverse engineer the 'Reciva Radio Application'. If you think you can help build this public information resource, please [http://sharpfin.zevv.nl/index.php?title=Special:Userlogin&returnto=Main_Page create an account]and get involved. = Using JTAG To Install an SSH Shell = The project purpose is to provide an alternative open source solution to the Reciva pro..."

This page only discusses the non-proprietary software running on the Barracuda module. We do *not* discuss or reverse engineer the 'Reciva Radio Application'.

If you think you can help build this public information resource, please [http://sharpfin.zevv.nl/index.php?title=Special:Userlogin&returnto=Main_Page create an account]and get involved.

= Using JTAG To Install an SSH Shell =

The project purpose is to provide an alternative open source solution to the Reciva proprietary software. In order to do this, access to the radio is needed. The following description details how this is achieved using JTAG to dump and restore a modified root image.

[[Software SSH Shell Activation]]

= GPL Firmware =

The reciva radio uses a distribution of Linux for the kernel / core, which is available from [http://www.reciva.com/gpl The Reciva Server]. Interestingly, there are several different releases that contain identically marked (and sized) tarfiles !

Several versions are available, and are summarised in the following table:

= Bootloader =

The good bootloader, found on the Riscstation is the [http://www.simtec.co.uk/products/SWABLE/ ABLE Bootloader], it is possible that this is the loader which is used on the radio module. This is the bootloader shipped with 'bast' platform Samsung 2410 Evaluation Board. The ABLE bootloader is proprietary software from Simtec Electronics. An open source project would have to replace this software with another bootloader such as Das U-Boot.

= Bootloader Information Resources =

* [http://www.aleph1.co.uk/book/print/310 ARM Bootloaders]

= Operating system and device drivers =
The Barracuda module runs [http://familiar.handhelds.org/ Familiar Linux]. Familiar Linux is a derivative of Debian Linux. Debian Linux has been [http://www.debian.org/ports/arm/ ported to several ARM platforms, including bast ]. The reference platform for bast is the [http://www.simtec.co.uk/products/EB2410ITX/spec.html Simtec Electronics EB2410ITX Evaluation Board].

Linux 2.4.26 is running on the ARM CPU within the Samsung device. Sourcecode for drivers for the following devices is acknowledge to be available :

* USB Host device
* PCM audio output
* UART
* 'BAST' real time clock
* I2C interface (what's on the bus?)
* IRDA driver for 'NSC PC87108/PC87338' (is this onboard?)
* LCD (tm13264cbcg / mg1203d / ...)

There is no network interface available onboard, a USB network adapter is used.

It seems that Reciva used the [http://www.debian.org/releases/stable/arm/ch02s01.html.en 'bast' ARM architecture] as a base for their own development.

"Bast is a modern ARM 920 board with a 266MHz Samsung processor. It has integrated IDE, USB, Serial, Parallel,
audio, video, flash and two ethernet ports. This system has a good bootloader which is also found on the CATS
and RiscStation systems."

(bast, cats, and riscstation are evaluation boards by Simtec Electronics)

Additional information about Linux on the 'bast' platform can be found [http://armlinux.simtec.co.uk/index.html here].

= System libraries + utilities =

The following libraries and applications will be needed at least for implementing radio software:

* C-library (glibc/uclibc?)
* Flash write/erase tools: mtd-utils
* Shell + basic unix tools (busybox!)
* codec libraries (libmad, libogg, libvorbis, libflac, etc)
* Support for WLAN and security: wireless tools and wpa_supplicant
* networking libraries for HTTP, RTP, RTSP, MMS, etc
* Webserver (boa?)
* Preferably a scripting language for rapid development and CGI scripts. Lua, perl, ruby ?

= 'Radio' application =

On top of all this, the 'radio application' will be running. This application might consist of various
processes, daemons, CGI-scripts, etc.

The main functions will be

* Handling of the user interface: LCD, buttons and led's
* Configuration of the device using a web server
* Network streaming + audio decoding. VLC for a quick start ?
* ...

== GPIO ==

The software source refers to the various GPIO signals: [[GPIOSignals]]

== I<sup>2</sup>C ==

GPIO provides sets of pins where the board can act as both an I2C master and a slave. Reciva say that [http://corporate.reciva.com/download_files/L1_06_SlaveModeOperation.pdf the module can be controlled over I2C] in slave mode, instead of a directly connected display and keyboard.

Software SSH Shell Activation

2025-06-08T12:23:55Z

Philipp: Created page with "== Enabling Login == '''REMINDER: The purpose of the project is to provide alternative firmware / patches to the reciva offering. The Sharpfin Project does not condone, and will not be party to any reverse engineering activities of any reciva application, the project deals with GPL code only.''' The NAND Flash in the reciva radio is partitioned into 5 areas: <pre> dev: size erasesize name mtd0: 00004000 00004000 "NAND BootAgent" mtd1: 000fc000 00004000 "Linux K..."

== Enabling Login ==

'''REMINDER: The purpose of the project is to provide alternative firmware / patches to the reciva offering. The Sharpfin Project does not condone, and will not be party to any reverse engineering activities of any reciva application, the project deals with GPL code only.'''

The NAND Flash in the reciva radio is partitioned into 5 areas:

<pre>
dev: size erasesize name
mtd0: 00004000 00004000 "NAND BootAgent"
mtd1: 000fc000 00004000 "Linux Kernel"
mtd2: 00d00000 00004000 "Root"
mtd3: 00100000 00004000 "Config"
mtd4: 00100000 00004000 "Debug"
</pre>

What we need to do is obtain the Root NAND partition, unpack it and add some files, repack it and upload it back into the radio.

* Use your favorite JTAG programmer to extract the Root partition to a file: 2ro
* Install jffs2 software
* Use unpack.jffs2 script to unpack the file
* untar the following over the unpacked tree
* Use mkfs.jffs2 to pack the file back up again
* Use your favorite JTAG programmer to reinstall the image

You will then be able to login as 'admin' password 'admin' onto your radio.

=== Install jffs2 software ===

<pre>
# cvs -d :pserver:anoncvs@cvs.infradead.org:/home/cvs login (password: anoncvs)
# cvs -d :pserver:anoncvs@cvs.infradead.org:/home/cvs co mtd
You may also need to install the gbootroot rpm to provide the blkmtd driver
</pre>

=== extract the root filesystem ===

Use the following script to unpack the root filesystem from the file 2ro in the current directory

<pre>
#!/bin/sh

modprobe loop
modprobe mtdblock

losetup /dev/loop0 2ro
insmod blkmtd erasesz=256 device=/dev/loop0
mkdir /mnt/mtd2
mount -t jffs2 /dev/mtdblock0 /mnt/mtd2

/bin/rm -rf mtd2
mkdir mtd2
(cd /mnt/mtd2 ; tar cf - . ) | (cd mtd2 ; tar xvf - )

umount /mnt/mtd2
rmmod blkmtd
losetup -d /dev/loop0
rmmod loop
rmmod mtdblock
rmmod mtdcore
</pre>

=== Unpack the dropbear tools into the tree ===

<< to be added >>

=== Use mkfs.jffs2 to pack the file back up again ===

<< to be added >>

== Links ==

* NAND Flash: http://www.linux-mtd.infradead.org/faq/nand.html
* JFFS2 Filesystem: http://www.linux-mtd.infradead.org/faq/jffs2.html
* JFFS2 Unpack Guide: http://www.yargybot.com/Familiar/BackupHowto.html

Single Phase And Three Phase

2025-06-08T12:22:59Z

Philipp: Created page with "dummy"

dummy

Sharpflash Bugs

2025-06-08T12:21:55Z

Philipp: Created page with "= Bugs = Please leave details of bugs and bug-fixes on this page, or chat about them on the discussion tab ... == Partition Overrun == Version: 0.1 Suspected Bug: If there are bad blocks, writing will overrun, and possibly corrupt next partition. Temporary fix: run sharpflash -b and reduce length in sharpflash -w command by 0x4000 * number of known bad blocks in partition. Permanent Fix: Truncate (lose) any blocks which overrun the specified length in the -w comman..."

= Bugs =

Please leave details of bugs and bug-fixes on this page, or chat about them on the discussion tab ...

== Partition Overrun ==

Version: 0.1

Suspected Bug: If there are bad blocks, writing will overrun, and possibly corrupt next partition.

Temporary fix: run sharpflash -b and reduce length in sharpflash -w command by 0x4000 * number of known bad blocks in partition.

Permanent Fix: Truncate (lose) any blocks which overrun the specified length in the -w command.

Issues: There may be issues with this - I don't understand how the device driver uses the flash - i.e. could it have an unused gap, then use the last block on the partition?

== Speed ==

Version: 0.1

The program is very slow - it can be speeded up several ways:

using a different scan chain to write to the processor memory - this would mean that the processor flash controller would write the ECC and 16 bytes instead of us doing it. The number of jtag clock ticks would probably also be less.

downloading a programmer program to the RAM, and also the code to be programmed. the programmer program can then write and check, thus reducing the involvement of jtag. OpenOCD has a lot of the code needed to do this.

== Corruption ==

Suspect that writes are dropping the odd byte here and there, so the resulting data is not what is wanted.

== More ... ==

SharpfinPatchfileStore

2025-06-08T12:21:07Z

Philipp:

The following files on the Sharpfin server are downloadable through the patchserver-launcher.exe programme.

* Sharpfin-uninstall 0.1.patch: https://www.sharpfin.org/images/7/71/Sharpfin-uninstall_0.1.patch
* Sharpfin-test.patch: https://www.sharpfin.org/images/9/9a/Sharpfin-test.patch
* Sharpfin-base 0.3.patch: https://www.sharpfin.org/images/c/c2/Sharpfin-base_0.3.patch
* Sharpfin-www 0.6.install: https://www.sharpfin.org/images/2/24/Sharpfin-www_0.6.install

These files are also available, but are untested alphas

* Sharpfin-base_0.4-alpha20080510.patch: https://www.sharpfin.org/images/2/26/Sharpfin-base_0.4-alpha20080510.patch