[Skyeye-developer] New update for PS7500FE
Alan Carvalho de Assis
acassis at gmail.com
Sun Jun 11 03:03:40 CST 2006
Hi Michael,
thank you to place it on current Skyeye.
This "test" program is not a common program. It is a bootloader develop by
Korean company Marusys to Daewoo, to be used on DSN-500M WebTV.
Marusys used software from WindRiver ($ strings bootstrap.bin)
This bootloader is used to download the OS firmware and to write it on
flash.
To see it you need get LCD on, LCD is running fine on Skyeye 0.8.7. If you
want I can send a screenshot to you.
Michael, I am searching how to debug binary only program (as this
bootstrap.bin) on GDB, but I only get info about debugging with source
(compiled with -g option).
But I don't have the source code to do it.
I found a tip suggest me to use objdump to disassembler it and after
assembler it newly with -g, but it bootloader is so much complex to me do
it.
Do you have some another suggestion ?
Have a nice weekend,
Alan
On 6/10/06, kang shuo <blackfin.kang at gmail.com> wrote:
>
>
>
> Sorry for waiting so long. Now I have commited your patch to the cvs
> repository. And we will add your testcase for ps7500 to our testsuite
> package so that we can make sure your testcase can run after every new
> SkyEye release.
>
> I just try to enable netcard simulation on ps7500 simulation. But I have
> not test for there seems no network program such as ping available in your
> test program.
>
> Now known issue is lcd simulation on ps7500 can not work. Maybe I can fix
> it in this week.
>
> The attachments is the latest cvs-build version of SkyEye and skyeye.confof
> ps7500.You can try it.
>
> - Thanks
> - Michael.Kang
>
> On 6/8/06, Alan Carvalho de Assis <acassis at gmail.com> wrote:
> >
> > Hi Kang,
> > I am sending the original patch (to skyeye-0.8.7) and my unfinnished
> > patch (to skyeye-1.2).
> >
> > Here is Danielson's tips I used to get it working:
> >
> > 1. I started with the 0.8.7 version from SourceForge. I chose
> > that version because it was smaller since it didn't contain
> > all the tc/tcl stuff for the GUI. Thus, building was much
> > faster.
> >
> > 2. Apply the patch:
> >
> > patch -p1 < skyeye-0.8.7.patch
> >
> >
> > 3 Build it (binaries end up in /usr/local/bin):
> >
> > ./configure --target=arm-elf --prefix=/usr/local
> > make
> > make install
> >
> > 4. Create a directory (I used ~/easybox/sim)
> > and put the following files in it:
> >
> > bootstrap.bin <-- this is your dump of the EEPROM
> > skyeye.conf <-- I included this in the email
> > uartin <-- You create this file using "mkfifo uartin"
> >
> > The file " skyeye.conf" contains the configuration of the machine
> > being simulated. If you look it over you will see that it
> > defines 8 memory banks for:
> >
> > eeprom
> > flash (I guessed at its address...I think I'm incorrect),
> > io space
> > ram bank1
> > ram bank2
> > ram bank3
> > ram bank4
> >
> > The rest of the file turns on the lcd simulation, defines a
> > file name for reading keyboard input from (the fifo "uartin"),
> > and the network stuff. The network stuff IP address
> > is set up now for option "3".
> >
> > The file "uartin" is a fifo. The skyeye emulator reads from this
> > file and you write to this file to simulate keyboard input (discussed
> > below).
> >
> > 5. You'll now need to become root again....
> >
> > 6. Make sure the "tun/tap" driver is running. On my system,
> > all I needed to do was:
> >
> > modprobe tun
> >
> > Do an "lsmod | grep tun" and you should see it loaded.
> > Also, "ls -lL /dev/net/tun" should show a device entry of
> > 10,200.
> >
> > 7. Now you can run skyeye:
> >
> > skyeye
> >
> >
> > It has a gdb interface. To load the simulator, type:
> >
> > target sim
> >
> > If that works, run things with:
> >
> > run
> >
> > 8. It will show it writing to the LED (IOCR) and
> > then after about 10-15 seconds (on my AMD 2700+ system),
> > the screen comes up....you may have to wait longer if
> > you have a slower system.
> >
> > 9. Once the screen comes up, you can simulate keyboard
> > input by opening an xterm window, cd'ing to the directory
> > where you have all the simulation files and typing:
> >
> > cat > uartin
> >
> > Then, type into that window and it will be as if
> > you typed it into the easybox. Note that since the
> > data is line-buffered, if you want to force a
> > non-CR-terminated line out, enter a "control-d".
> >
> > So, to select option 2, you'd type "2" followed
> > by "control-d". To enter all the other lines,
> > just type them, ending them with a carriage return.
> >
> > At this point it will try and use the network interface.
> > You can see what's being sent, by using tcpdump and
> > specifying the interface tun0.
> >
> > As I mentioned, I haven't yet got the network simulation
> > to work correctly....it doesn't seem to get the correct
> > mac addresses and after it receives, it doesn't seem
> > to think it has received anything since it doesn't
> > read the data from the simulated ethernet chip....
> >
> > I have lots of output coming to the gdb terminal window
> > showing all the writes to the ethernet chip, and video
> > chip, etc. Note the writes at 0x8000xxxx. I think this
> > is where the flash might be...those writes look like
> > flash enable/reset codes...
> >
> > Most of my changes are in the file sim/arm/skyeye_mach_ps7500.c.
> > I fiddled a little with the interrupt stuff for the network
> > simulation also. The diff file should give you an idea of
> > what I've been changing. You might want to look at those
> > accesses in the 0x8000xxxx area and see if it makes any sense
> > for the type of flash that the Easybox has. Note that probaby
> > the address offsets need to be divided by 4 to make things
> > make sense. In other words, 0x8000004 would be offset 0x0001.
> > I'm not sure why some of the accesses are at 0x8000xxxx and
> > some at 0x8200xxxx. It looks to be reading the chip id
> > from the flash. The reason the data is repeated twice
> > is that there are two flash chips....
> >
> > That is all!
> >
> > All is running fine on original patch, except the network.
> > That bootstrap firmware (512KB) is the BIOS of WebTV, it is used to load
> > the OS' firmware to flash. I want use network to do BIOS load the OS
> > firmware.
> >
> > I want understand the OS' firmware format to create a Linux Image in
> > this format to place Linux into WebTV with no BIOS modification.
> >
> > Alan
> >
> > P.S.: If you want I can send the OS too, I don't send it because it is
> > bigger.
> >
> >
> > On 6/7/06, kang shuo <blackfin.kang at gmail.com> wrote:
> > >
> > > I like to try it. You can send your patch to the maillist...Now
> > > SkyEye has a common hardware simulation framework.Network should be
> > > work on any simulation.
> > >
> >
> >
> > _______________________________________________
> > Skyeye-developer mailing list
> > Skyeye-developer at lists.gro.clinux.org
> > http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
> >
> >
> >
> >
>
> _______________________________________________
> Skyeye-developer mailing list
> Skyeye-developer at lists.gro.clinux.org
> http://lists.gro.clinux.org/cgi-bin/mailman/listinfo/skyeye-developer
>
>
>
>
--
------------------------------------------------------------
| Alan Carvalho de Assis |
------------------------------------------------------------
--
Não importa o que os outros irão pensar,
A cura para a infelicidade é a felicidade
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gro.clinux.org/pipermail/skyeye-developer/attachments/20060610/a8701c28/attachment.htm
More information about the Skyeye-developer
mailing list