Re: [Qemu-discuss] Coldfire 5282 Support

Thanks Peter - thoughts below. > On Oct 25, 2017, at 9:51 AM, Peter Maydell wrote: > > On 25 October 2017 at 15:36, William Mahoney wrote: >> >>> On Oct 25, 2017, at 1:37 AM, Peter Maydell wrote: >>> >>> On 24 October

Re: [Qemu-discuss] Coldfire 5282 Support

> On Oct 25, 2017, at 1:37 AM, Peter Maydell wrote: > > On 24 October 2017 at 21:34, William Mahoney wrote: >> Quick question. On the MCF5282 there is a huge memory mapped IO starting at >> 0x4000 and going for 1A. All of the IO is

Re: [Qemu-discuss] Coldfire 5282 Support

OK I took a look at slirp.c as you suggested. I put in some fprintf’s in slip.c for the ARP requests and also in arp_table_add and arp_table_search in arp_table.c. In the process I learned a lot about how the ARP services work within QEMU and in the process also realized what I was doing wrong.

Re: [Qemu-discuss] Coldfire 5282 Support

OK so really even though I see the driver sending the ARP requests, they’re not actually ever making it to the host, even though the PCAP file shows them. In other words, the PCAP file is "on the guest side" of the connection not "the host side of the connection". Correct? If that’s the case

Re: [Qemu-discuss] Coldfire 5282 Support

Hi Thomas; I was telling this to Peter as well offline. The initial problem just FYI was that the routing on the m68k side was nonexistent, so it wasn’t even sending anything to the net drivers at all. I turned on the debugging in the net driver and there was no traffic. It looks like there is

Re: [Qemu-discuss] Coldfire 5282 Support

On 15 September 2017 at 21:41, William Mahoney wrote: > 3) Can of worms. The 5282 allows you to move the base address > of the control registers, the start address of the SRAM, all > sorts of things. The control registers are all offset from a > default address when the

Re: [Qemu-discuss] Coldfire 5282 Support

Le 13/09/2017 à 19:48, Thomas Huth a écrit : > On 13.09.2017 16:31, William Mahoney wrote: > [...] >> By the way, there is a link to a uClinux image on the emu documentation >> pages but the link times out. Is there a uClinux 5208 kernel image somewhere >> else? I only wanted to try that to make

Re: [Qemu-discuss] Coldfire 5282 Support

On 13.09.2017 16:31, William Mahoney wrote: [...] > By the way, there is a link to a uClinux image on the emu documentation pages > but the link times out. Is there a uClinux 5208 kernel image somewhere else? > I only wanted to try that to make sure that everything else (serial ports) is > set

Re: [Qemu-discuss] Coldfire 5282 Support

> On Sep 13, 2017, at 3:34 AM, Thomas Huth wrote: > > On 12.09.2017 21:05, William Mahoney wrote: >> OK a bit of an update and another question or two. First, you’re right, “it >> just plain works”. What I’d like to verify today is that I am “doing the >> right thing” is

Re: [Qemu-discuss] Coldfire 5282 Support

On 12.09.2017 21:05, William Mahoney wrote: > OK a bit of an update and another question or two. First, you’re right, “it > just plain works”. What I’d like to verify today is that I am “doing the > right thing” is all. > > 1) I made a copy of qemu/hw/m68k/mcf5208.c as mcf5282.c and I - for

Re: [Qemu-discuss] Coldfire 5282 Support

OK a bit of an update and another question or two. First, you’re right, “it just plain works”. What I’d like to verify today is that I am “doing the right thing” is all. 1) I made a copy of qemu/hw/m68k/mcf5208.c as mcf5282.c and I - for now - changed all 5208 to 5282 inside the source. Threw

Re: [Qemu-discuss] Coldfire 5282 Support

On 8 September 2017 at 21:32, William Mahoney wrote: > "digic_load_rom()" knows the filename via an extern “bios_name” which is at > “include/sysemu/sysemu.h” but really lives in “vl.c”. It is set based on > “machine_ops” that comes from “qemu_get_machine_opts()” which in

Re: [Qemu-discuss] Coldfire 5282 Support

I thought I would look at the -bios first and I had some time this afternoon. If you’re the right age group you will understand when I say "YOU ARE IN A MAZE OF TWISTY LITTLE PASSAGES, ALL ALIKE”. "digic_load_rom()" knows the filename via an extern “bios_name” which is at

Re: [Qemu-discuss] Coldfire 5282 Support

On 06.09.2017 00:04, William Mahoney wrote: > >> On Sep 5, 2017, at 4:37 PM, Peter Maydell wrote: >> >> On 5 September 2017 at 20:30, William Mahoney wrote: [...] >>> I’d like to find this and/or anything else to clue me in before >>> starting as

Re: [Qemu-discuss] Coldfire 5282 Support

> On Sep 5, 2017, at 4:37 PM, Peter Maydell wrote: > > On 5 September 2017 at 20:30, William Mahoney wrote: >> Thanks Thomas. One more question. Somewhere there must be a "what >> parts to look for where” document. You know, a “If you are

Re: [Qemu-discuss] Coldfire 5282 Support

> On Sep 4, 2017, at 3:11 AM, Thomas Huth wrote: > > On 01.09.2017 21:03, William Mahoney wrote: >> Hello QEMU users. >> >> I am interested in looking into a port for the Motorola Coldfire 5282. I saw >> that others in the Coldfire family were supported, like the 5208 eval

Re: [Qemu-discuss] Coldfire 5282 Support

On 01.09.2017 21:03, William Mahoney wrote: > Hello QEMU users. > > I am interested in looking into a port for the Motorola Coldfire 5282. I saw > that others in the Coldfire family were supported, like the 5208 eval board > and the 5206 as a bare CPU. When I started looking into it I saw that

[Qemu-discuss] Coldfire 5282 Support

Hello QEMU users. I am interested in looking into a port for the Motorola Coldfire 5282. I saw that others in the Coldfire family were supported, like the 5208 eval board and the 5206 as a bare CPU. When I started looking into it I saw that several files (e.g. coldfire/flexcan.h and