[s1mp3-dev] RES: Loadram plus original firmware = impossible!

[seventh guardian]

On 6/21/06, Bluechip <csbluechip at gmail.com> wrote:
>
> >What about disassembling the "loader" firmware code to figure it out? Too
> >much work just to know that?
>
> Yes, probably, but it's not "too much work" on a more general level.
> That is, the information procured from such an exercise would have a
> value above and beyond that for which is was performed.
>
> I think, on a side note, it may be a worthy exercise.
> I think this is the future of the s1mp3 project.
> I genuinely do not believe Swan will ever exist.
> Certainly not for the 20xx chips.
> And I bet my life ...not before the 20xx chips go obselete.
>
> I recently spoke (separately and unleadingly) to two techie friends
> (one a "guru", the other "just does it for a living") ...the
> conversation on both occasions went something like:
> BC: "If you had to write a kernel+apps for an embedded device; where
> would you start?"
> Other: "Well, you spec the api and then ...."
> [I mean literally _that blunt_
> ...they both hesitated over what way to go from there
> ...but step 1 was unarguable]
> I can find NOBODY AT ALL that can think of any other way to do it.
> As this [API] is not a thing which can be made to happen efficiently
> in this environment,
> I think time and effort should be invested in interfacing with what
> is already there.
> Find some way to load an App from NAND and just write pretty stuff
> for the fun of it.
>
> The 20xx chips will be obselete in less than 6 months.
> If you really think that you wish to improve Actions' sales figures
> by writing firmware for them,
> wait for the 21xx series players and don't hang about debating such as:
> "How shall we define NULL" [yes, I'd like to make it obvious that I
> am as guilty as the next man]
> "Which license should we use"
> "Let's faction the group into smaller pieces"
> "What colour should the logo be"
> "Will somebody lead this project please"
> "Let's rename the site"
> "Which license should we use"
> "Let's have an anarchy based system of teamwork" [see: irony]
> "Let's write software we can download for free"
> etc.

I'm not buying a new player in the near future, so I'm not in a hurry.

>
> I would, in your shoes, dedicate the next 6 months to coming up with
> a plan that does not require an API before people can code.
>
>
> This group has ALL the skills it needs.  Web designers.  UI
> designers.  Techie gurus.  Legal advisor.  UI coders.  Kernel
> coders.  Electronics engineers.  etc.
>
> It has truly broken my spirit watching this project die ...Try to
> salvage what you can from what is left.
>
> BC
>
>
>
> >Mateus M. Del Bianco
> >Del Bianco Networks
> >-----Mensagem original-----
> >De: s1mp3-dev-bounces at s1mp3.org [mailto:s1mp3-dev-bounces at s1mp3.org] Em nome
> >de Bluechip
> >Enviada em: quarta-feira, 21 de junho de 2006 13:35
> >Para: S1mp3.org - SWAN development
> >Assunto: Re: [s1mp3-dev] Loadram plus original firmware = impossible!
> >
> >
> >Maybe the file is overlaid
> >Maybe we don't know about the addressing system properly
> >Maybe some of it lives in ROM
> >errrr, that's all I can come up with for now
> >
> >BC
> >
> >
> >Ok, i thought for the fun of it, i would run some of the firmware's original
> >ap files through loadram.
> >
> >unable to run tester.ap i tried music.ap (it is a 65k file) when i run it in
> >loadram i get this:
> >
> >C:\download\loadram- v0.3.3-ALL\loadram-v0.3.3-ALL\win32-bin>loadram
> >2ndstage.bin
> >  MUSIC.AP
> >found 4 busses
> >device_open(): device found
> >Running the program...
> >Loading data to send to second stage loader...
> >Files >64K don't fit in the z80 address space, silly.
> >Uploading second binary...
> >Error sending: No error
> >Done
> >
> >How can this be, the player is using an ap bigger than the ram can
> >handle?!?!
> >
> >--
> >Ian Hawdon (ian_hawdon)
> >
> >http://www.s1mp3.org (SWAN's home page)
> >_______________________________________________
> >s1mp3-dev mailing list
> >s1mp3-dev at s1mp3.org
> >http://s1mp3.org/mailman/listinfo/s1mp3-dev_s1mp3.org
> >
> >
> >_______________________________________________
> >s1mp3-dev mailing list
> >s1mp3-dev at s1mp3.org
> >http://s1mp3.org/mailman/listinfo/s1mp3-dev_s1mp3.org
>
>
> _______________________________________________
> s1mp3-dev mailing list
> s1mp3-dev at s1mp3.org
> http://s1mp3.org/mailman/listinfo/s1mp3-dev_s1mp3.org
>