qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v3 0/1] tricore: added triboard with tc27x_soc
@ 2020-06-22 13:19 David Brenken
  2020-06-22 13:19 ` [PATCH v3 1/1] " David Brenken
  0 siblings, 1 reply; 5+ messages in thread
From: David Brenken @ 2020-06-22 13:19 UTC (permalink / raw)
  To: qemu-devel; +Cc: kbastian, Andreas Konopik

From: Andreas Konopik <andreas.konopik@efs-auto.de>

Hello everyone,

this patch adds the AURIX TC277 D-Step TriBoard as QEMU machine
(-M AURIX_TriBoard_TC277D). Memory maps are implemented according to the
"AURIX TC27x D-Step User's Manual V2.2 2014-12". AURIX memory layouts
are specified by the processor, that is why this patch has been reworked as a
SoC-implementation for v2. Patch v3 added sizes to memory mappings.

Andreas Konopik (1):
  tricore: added triboard with tc27x_soc

 hw/tricore/Kconfig             |   8 ++
 hw/tricore/Makefile.objs       |   2 +
 hw/tricore/tc27x_soc.c         | 246 +++++++++++++++++++++++++++++++++
 hw/tricore/triboard.c          | 102 ++++++++++++++
 include/hw/tricore/tc27x_soc.h | 139 +++++++++++++++++++
 include/hw/tricore/triboard.h  |  53 +++++++
 6 files changed, 550 insertions(+)
 create mode 100644 hw/tricore/tc27x_soc.c
 create mode 100644 hw/tricore/triboard.c
 create mode 100644 include/hw/tricore/tc27x_soc.h
 create mode 100644 include/hw/tricore/triboard.h

-- 
2.27.0



^ permalink raw reply	[flat|nested] 5+ messages in thread
* Re: [PATCH v3 1/1] tricore: added triboard with tc27x_soc
@ 2020-06-30 10:28 Konopik, Andreas (EFS-GH2)
  2020-07-01  8:46 ` Bastian Koppelmann
  0 siblings, 1 reply; 5+ messages in thread
From: Konopik, Andreas (EFS-GH2) @ 2020-06-30 10:28 UTC (permalink / raw)
  To: Bastian Koppelmann, David Brenken
  Cc: Hofstetter, Georg (EFS-GH2), Brenken, David (EFS-GH5),
	Rasche, Robert (EFS-GH2), qemu-devel@nongnu.org,
	Biermanski, Lars (EFS-GH3)

Hi Bastian,

> On Mon, Jun 22, 2020 at 03:19:34PM +0200, David Brenken wrote:
> > From: Andreas Konopik <andreas.konopik@efs-auto.de>
> > +const MemmapEntry tc27x_soc_memmap[] = {
> > +    [TC27XD_DSPR2]     = { 0x50000000,   0x1E000 },
> > +    [TC27XD_DCACHE2]   = { 0x5001E000,    0x2000 },
> > +    [TC27XD_DTAG2]     = { 0x500C0000,     0xC00 },
> 
> The size changed from 0xa00 to 0xc00 from v2. The manual states that it has no
> size. I guess you inferred the size from the address range. How does real hw
> behave if you access DTAG2?

DTAG size of 0xa00 was a mistake, 0xc00 is correct. Even though the manual does not assign sizes, DTAG and PTAG can be mapped for memory testing purposes.
Therefore memory accesses to DTAG/PTAG are possible (see Footnote 3 & 4 [1, Page 3-10]).

Real hardware has to be configured via MTU before accessing DTAG/PTAG. Because QEMU tricore has no MTU, we wanted to be less restrictive by mapping DTAG/PTAG into memory.

> Why not use KiB/MiB sizes as before? I created a patch for that. Can you check
> that I didn't skrew up the sizes?

Thank you, the patch looks good to me.
How do you want to proceed? Should we send you a Patch v4?

> The remainder looks good to me.

Great!

Kind regards,

Andreas

[1] https://hitex.co.uk/fileadmin/uk-files/downloads/ShieldBuddy/tc27xD_um_v2.2.pdf


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-07-01  8:47 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-06-22 13:19 [PATCH v3 0/1] tricore: added triboard with tc27x_soc David Brenken
2020-06-22 13:19 ` [PATCH v3 1/1] " David Brenken
2020-06-24  8:26   ` Bastian Koppelmann
  -- strict thread matches above, loose matches on Subject: below --
2020-06-30 10:28 Konopik, Andreas (EFS-GH2)
2020-07-01  8:46 ` Bastian Koppelmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).