Rockbox mail archiveSubject: Re: Sansa radio driver (AS5314 help
Re: Sansa radio driver (AS5314 help
From: Antonius Hellmann <antonius.hellmann_at_gmx.de>
Date: Wed, 16 May 2007 19:57:16 +0200
If you can hear any sound, then I would assume, that the device is working.
So nothing more to be done with the radio init/powerup.
I bet, that the audio configuration is not correct yet.
In the emu I found following AS3514 init sequence after entering the radio
and after setting up the tuner:
70000084 |= 1 <<<<< don't know, wether this is radio related
70000080 |= 4 <<<<< don't know, wether this is radio related
And regarding your other question:
69ddd55 0000e8f4 CPU ???????? 70000020 R4-40000000
69ddd57 0000e8fc CPU ???????? 70000020 W4-40000000
I added the comment after looking at the assembler code at addr 0000e8f4.
The cpu reads a value from 0x70000020, bics bit11 and stores the result.
Nothing wrong here.
----- Original Message -----
From: "Ivan Zupan" <zivan56_at_iwdstudio.com>
To: "Rockbox development" <rockbox-dev_at_cool.haxx.se>
Sent: Wednesday, May 16, 2007 2:18 PM
Subject: Re: Sansa radio driver (AS5314 help
> The radio commands are well figured out. I have set the audio to maximum
> output for the FM chip and maximum gain for the AS3514, but it is still
> barely audible. I am almost certain that something is blocking the audio
> output from the FM chip. Maybe the init is done right when the firmware
> start up and this only enabled something else? DEV_INIT &= ~(1 << 11)
> seems to have no effect on the radio, there is also a reference to
> 70000030 right before this from a log I found:
> 0392304 0000333c 70000030 R-00000000
> 0392306 00003344 70000030 W-40000000
> 0392308 0000334c 70000020 R-40000000
> 039230b 00003358 70000020 W-40000000
> Writing that value to that memory resulted in the screen fading out to
> purple. How does clearing bit 11 from the value 0x40000000 result in
> 0x40000000 from your logs? Or is this the emulator modifying the actual
> There is a clock input 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. Perhaps the
> clock in double as power for amplification?
> Antonius Hellmann wrote:
>> Yes, that is correct. The complete register accesses look as follows:
>> 69a7b08 000b9418 CPU GPI_F_VAL 6000d0b4 R4-0000003b <<<< right click
>> detection (into radio menu)
>> 69ddd55 0000e8f4 CPU ???????? 70000020 R4-40000000 <<<< reading
>> 69ddd57 0000e8fc CPU ???????? 70000020 W4-40000000 <<<< bic bit
>> 11 of DEV_INIT
>> .... as posted before .....
>> If it is of interest to you, I can dump the sansa radio commands in a
>> more readable way.
>> But be aware, that the radio responses are synthetic in the emulator.
>> ----- Original Message ----- From: "Ivan Zupan" <zivan56_at_iwdstudio.com>
>> To: "Rockbox development" <rockbox-dev_at_cool.haxx.se>
>> Sent: Wednesday, May 16, 2007 2:38 AM
>> Subject: Re: Sansa radio driver (AS5314 help
>>> I have tried those, but they are pretty much what Mr.H described.
>>> Interestingly enough, he mentioned clearing bit 11 at 0x70000020 (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 line1 in via
>>> some hardware switch...
Received on 2007-05-16