Custom Query (93 matches)
Results (10 - 12 of 93)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#27 | fixed | Multi-processor platform with several loaders | ||
Description |
Hi, I am trying to write a multi-processor platform with private program memories, and I was trying to figure out if this was possible with SOCLIB. I made a try with 2 Mips in a first phase, with two associated mapping tables. The difference between both mappings is the MEMORY address, 0x10000000 for Mips0 and 0x20000000 for Mips1. I created two loaders taking different binaries, the reset section of the first jumps to 0x10xxxx and the second jumps to 0x20xxx. Loader loader0("MJPEG0.x"); VciRam<vci_param> vcimultiram0("vcimultiram0", IntTab(0,0), maptab, loader0); Loader loader1("MJPEG1.x"); VciRam<vci_param> vcimultiram1("vcimultiram1", IntTab(1,0), maptab1, loader1); MJPEG0.x: 211735 bfc00020: 3c1b1001 lui k1,0x1001 211736 bfc00024: 277bf360 addiu k1,k1,-3232 MJPEG1.x: 202290 bfc00020: 3c1b2001 lui k1,0x2001 202291 bfc00024: 277bb820 addiu k1,k1,-18400 However, when I execute the simulation, I see that cache1 seems to execute the reset section of MJPEG0.x. cache0 PC: 0xbfc00020 NPC: 0xbfc00024 Ins: 0x3c1b1001 cache0 PC: 0xbfc00024 NPC: 0xbfc00028 Ins: 0x277bf360 cache1 PC: 0xbfc00020 NPC: 0xbfc00024 Ins: 0x3c1b1001 cache1 PC: 0xbfc00024 NPC: 0xbfc00028 Ins: 0x277bf360 Did I do something wrong? Thank you Alexandre |
|||
#24 | fixed | caba-vgmn-vcache_multi_timer-iss2_mipsel platform: segmentation fault | ||
Description |
When I execute the caba-vgmn-vcache_multi_timer-iss2_mipsel platform, the simulation results a segmentation fault. The backtrace provided by gdb is presented bellow: [Thread debugging using libthread_db enabled] [New process 15938] SystemC 2.2.0 --- Sep 19 2008 14:58:49 Copyright (c) 1996-2006 by all Contributors ALL RIGHTS RESERVED [New Thread 1115856 (LWP 15938)] [Detaching after fork from child process 15941. (Try `set detach-on-fork off'.)] [Detaching after fork from child process 15943.] [Detaching after fork from child process 15945.] [Detaching after fork from child process 15947.] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1115856 (LWP 15938)] 0x002fc13b in ____strtol_l_internal () from /lib/libc.so.6 |
|||
#55 | fixed | STORE_COND et READ_LINKED Data Access | ||
Description |
Existe t-il une documentation sur ces modes d'accès aux données ? STORE_COND utilise pour son implémentation la commande VCI CMD_NOP Quel est le protocole de transfert de cette pseudo commande VCI ? |