Hello, does anybody know why the peripherals clock is not working when simulating my application with Crosswork Debug? My board is an Olimex OKI-H5003, with an ARM7TDMI Oki core. I want to specify that the application is working fine on the board, so the code is ok. I just want to simulate the application to see what actually happens but none of the peripherals is working (already tried with UART, System Timer and Timer0), that's why I thought about the peripherals clock: it's the only common thing to all the peripherals. The rest of the program is working, only the peripherals are stucked. Thank to anybody who will be able to help. -- 1N French fries? Fried, boiled, stabbed...just kill 'em all.
Rowley Crosswork Debug and CCLK
Started by ●November 28, 2011
Reply by ●November 28, 20112011-11-28
On Mon, 28 Nov 2011 23:27:42 +1100, 1N <N1@1N.gnugna> wrote:>Hello, >does anybody know why the peripherals clock is not working when >simulating my application with Crosswork Debug? > >My board is an Olimex OKI-H5003, with an ARM7TDMI Oki core. >I want to specify that the application is working fine on the board, so >the code is ok. I just want to simulate the application to see what >actually happens but none of the peripherals is working (already tried >with UART, System Timer and Timer0), that's why I thought about the >peripherals clock: it's the only common thing to all the peripherals. >The rest of the program is working, only the peripherals are stucked.The simulator handles the ARM V4T, ARM V5TE, ARM V6-M and ARM V7-M instruction sets but it does not attempt to model all of the various peripherals, interrupt controllers, clock domains, or internal bus structures of each of chips. It's essentially just the ARM core. Individual manufacturers may release debugger/simulators for their own product lines (e.g., Atmel's AVR Studio) but it's not possible, economically, for a third-party vendor to do so. Simulators in general are kind of iffy, IMHO. Unless they are correct down to the individual clock cycle they can be more misleading than illuminating. Very hard to do correctly for a complex chip. -- Rich Webb Norfolk, VA
Reply by ●November 30, 20112011-11-30
On 28/11/2011 12:27, 1N wrote:> Hello, > does anybody know why the peripherals clock is not working when > simulating my application with Crosswork Debug? > > My board is an Olimex OKI-H5003, with an ARM7TDMI Oki core. > I want to specify that the application is working fine on the board, so > the code is ok. I just want to simulate the application to see what > actually happens but none of the peripherals is working (already tried > with UART, System Timer and Timer0), that's why I thought about the > peripherals clock: it's the only common thing to all the peripherals. > The rest of the program is working, only the peripherals are stucked. > > Thank to anybody who will be able to help. >I don't know for absolute, but it would be normal for a GCC based simulator to be an instruction set simulator, and, if you like, a core simulator. It will not simulate the chip into which the core is placed, so will know nothing about the clock set up. Check with Rowley support to be sure though. Regards, Richard. + http://www.FreeRTOS.org Designed for Microcontrollers. More than 7000 downloads per month.
