Am I right, that after Zagor's makefile rework the optimization level -O2 has
vanished?
Or is there a reason to not activate the compiler optimization?
Tony
I would like to add the arm disassembler to rockbox svn.
The tools directory may be reserved for real rockbox development.
So are there any objections to adding a new utils directory on the
topmost rockbox level (i.e. apps, firmware, tools, ..., +utils)?
I would then store the disassembler to: util
Based on an idea of jhMikeS I modified svn code (i2s-pp.c) in the following way:
// IISFIFO_CFG |= 0x33; /* 12 slots full/empty config */
/* Bit2-3, Bit6-7 seem to have no meaning */
IISFIFO_CFG |= 0x22; /* 8 slots full/empty config */
which solves the channel swapping issues. The modific
to the tuner, perhaps it needs to be enabled like
on the AS chip? However, according to the Sanyo specification, it does
not necessarily have to be used.
Overall, it's quite strange that I am able to get correct results from the
Sanyo chip (revision, status, etc), yet audio is very faint. P
it 11 at 0x7020 (no effect
on the radio whatsoever by the way). This address appears to be DEV_INIT.
Since all the hardware uses DEV_EN/DEV_INIT/DEV_RS, maybe the radio is not
enabled at all? Do you see any references to the above right before GPIOH
is used? It may be used to unmute the
I ran the sansa emulator into the radio menu. This is the result:
Directly after entering the radio menu the sansa emulator does a lot of
accesses to the GPIO-H registers.
Probably this can give a hint, how to configure the output? But it may be
only relevant for detecting the radio hardware.
R
I just checked your patch. One idea:
Probably the reading/writing of the gpio input generates another interrupt,
which in turn again accesses the gpio register? If I have it right, then the
original software disables the interrupt (GPIOH_INT_CLEAR), before reading
the registers and reenables th
when needed? I _am_ rather new to ARM and such but it's my educated guess
atm based on our other big CPU. I fear major complication from it.
- Original Message -
From: Antonius Hellmann
To: Rockbox development
Sent: Wednesday, May 09, 2007 2:03 AM
Subject: PPs r
One idea, why we have these troubles with interrupt handling on the PP devices
is, that probably the supervisor mode has some issues with interrupt switching?
I understand, that the supervisor mode makes it easy to do register
manipulations. But it might be more safe to run the rockbox applicati
R1 and other core specific handlers should be used.
- Original Message -
From: Antonius Hellmann
To: Rockbox development
Sent: Tuesday, May 08, 2007 5:08 AM
Subject: Sansa (PP502x?) GPIO interrupts in rockbox software
I evaluated the cop interrupts in the current rockb
I evaluated the cop interrupts in the current rockbox software:
After enabling the interrupts on the cop (resetting bit7 in the corresponding
cpsr)
The TIMER1 interrupts correctly lead to a call to irq().
But there are two interesting things:
1. During the measurement period the corresponding COP_
I evaluated the cop interrupts in the current rockbox software:
After enabling the interrupts on the cop (resetting bit7 in the corresponding
cpsr)
The TIMER1 interrupts correctly lead to a call to irq().
But there are two interesting things:
1. During the measurement period the corresponding COP_
I did a first attempt in finding the magics of the sd card detection in the
sansa software by using the emulator.
Here are the results:
>From the debug screen: GPIOA bit7 (0x80) goes low on sd card insertion.
The sansa software executes gpio in interrupt context. I think I have
identified follo
Ok, I will put the source to the patch tracker soon.
Toni
- Original Message -
From: "Paul Louden" <[EMAIL PROTECTED]>
To: "Rockbox development"
Sent: Wednesday, January 10, 2007 10:15 PM
Subject: Re: Sansa e2x0 emulator for Windows
I'd like to just reinforce Daniel Ankers' reques
I'm working on a win based sansa emulator.
Until now I have done following components (rockbox used functionality only!):
- emulate cpu
- emulate ata (read only functionality)
- emulate display
- emulate memory
- emulate keys
- emulate timers
- log the executed code to disassembler file (inc
15 matches
Mail list logo
