Hi Daiki,

I was using mbed-src_GR-PEACH_rev_b, not the mbed library

I had to keep mbed-src_GR-PEACH_rev_b . mbed-src from your link above compiled ok, but the GR-PEACH board would not even start. Is it because I have a rev B board?

1. When I disabled L2 cache only, the erroneous numbers declined significantly, but not completely.

2. When I disabled all caches, the erroneous numbers got way worse!!!

3. When I enable only the Instruction cache, like 2. above, the erroneous numbers got way worse.

4. When I enable only the Data cache, like 2. and 3. above, the erroneous numbers got way worse.

5. When I enable the Data and L2 caches (Instruction cache disabled), the erroneous numbers were about the same as when all caches are enabled.

6. When I enable the Instruction and L2 caches (Data cache disabled), the erroneous numbers were about the same as when all caches are enabled.

7. When I disabled data and instruction caches, but L2 cache enabled, the erroneous numbers were about the same as with all caches enabled.

8. The printf statements (from above) detect the enable/disable caches correctly.

Q1. Is there an equivalent printf available for detecting L2 cache enabled/disabled?

Q2: Is there a way to disable the internal FPU and use an external floating point library?

For the rev.B board, it should work by the following way.
・Replace your "mbed-src\taregets\hal\TARGET_RENESAS\TARGET_RZ_A1H\PinNames.h" with PinNames.h for GR-PEACH rev.B.


A1. To check whether L2 cache is enabled, you need to change some files.

extern int PL310_GetEnable (void);

//Get L2 cache enable bit
int PL310_GetEnable (void) {
    return PL310->CONTROL;
}

#include "mbed.h"
#include "pl310.h"

DigitalOut myled(LED1);

int main() {
    while(1) {
        myled = 1;
        wait(0.2);
        myled = 0;
        wait(0.2);
        if (( PL310_GetEnable() & 0x01 ) != 0 ) {
            printf ("L2 cache is enabled.\n");
        } else {
            printf ("L2 cache is disabled.\n");
        }
    }
}

A2. In online compiler, you can not use external floating point library because compile options are fixed.
If you export your program and use offline compiler, you can change compile options and use external floating point library.

Uninitialized variables is something I do not do (at least I don't think I do). Not to say that libraries I import may have done so. I've been writing code on mbed since 2009. Granted, they are all Cortex M cores.

By uninitialized, what specifically do you mean? I am not specifically pushing popping items from the stack. Can you give a couple codes examples of what this issue could be or what I should be looking for?

Stack variables are just local variable declared inside a method or block of code. Here a simple example.

int foo(int bar, int bert) {
    int bill; // variable uninitialized.

    if (bar > 0} {
        bill= bar;
    }

    if (bill> bert) { // bill not initialized if bar > 0.
        .....
    }

   return bill;
}

GR-PEACH team,

Any update on this?