Petr Slansky

YES, it works. These options are better: sdcc --iram-size 128 --no-xinit-opt demo.c Problem is that SDCC clears RAM during init, this code is troublemaker on STC15F104W: L0003: CLR A MOV R0, #FFh L0012: MOV @R0, A DJNZ R0, L0012 LJMP L0004 STC15F104W has only 128B of RAM and it seems that it maps address 0xff to 0x7f, 0xfe to 0x7e, etc. When the value in R0 reaches 0x80, it writes value 0x00 to address 0x00 (0x80 maps to 0x00) and because R0 is at address 0x00, neverending loop is created. It was...

YES, it works. These options are better: sdcc --iram-size 128 --no-xinit-opt demo.c Problem is that SDCC clears RAM during init, this code is troublemaker on STC15F104W: L0003: CLR A MOV R0, #FFh L0012: MOV @R0, A DJNZ R0, L0012 LJMP L0004 STC15F104W has only 128B of RAM and it seems that it maps address 0xff to 0x7f, 0xfe to 0x7e, etc. When the value in R0 reaches 0x80, it writes value 0x00 to address 0x00 (0x80 maps to 0x00) and because R0 is at address 0x00, neverending loop is created. This was...

Is there a way to tell SDCC that MCU has only 128B of RAM? I tried to create a simple blink program for STC15F104W and it was not working (LED at port P3, simple neverending while loop with delays). The same program was working on STC15F204EA (that has 256B of RAM). It was not clear from log files (map, sym, asm, etc) but SDCC uses silently internal RAM with addresses 128-255B, to pass parameters to function and during MCU initialisation. That was tricky to find this source of trouble so I assumed...

Is there a way to tell SDCC that MCU has only 128B of RAM? I tried to create a simple blink program for STC15F104W and it was not working (LED at port P3, simple neverending while loop with delays). The same program was working on STC15F204EA (that has 256B of RAM). It was not clear from log files (map, sym, asm, etc) but SDCC uses internal RAM with addresses 128-256B, to pass parameters to function and during MCU initialisation. That was tricky to find this source of trouble so I assumed for long...

Is there a way to tell SDCC that MCU has only 128B of RAM? I tried to create a simple blink program for STC15F104W and it was not working (LED at port P3, simple neverending while loop with delays). The same program was working on STC15F204EA (that has 256B of RAM). It was not clear from log files (map, sym, asm, etc) but SDCC uses internal RAM with addresses 128-256B, to pass parameters to function and during MCU initialisation. That was tricky to find this source of trouble so I assumed for long...

This tool is just a toy! Everything is hardcoded and difficult to change by end user... :-( An example of JDBC string to connect to AWS Aurora cluster (https://stackoverflow.com/questions/56403686/aurora-mysql-jdbc-fail-over) jdbc:mysql:replication://master.xxxx.rds.amazonaws.com:3306,read.xxxx.rds.amazonaws.com:3306/dbnamerhere?autoReconnect=true&logger=com.mysql.jdbc.log.Slf4JLogger&allowSlavesDownConnections=true&readFromMasterWhenNoSlaves=true&loadBalanceBlacklistTimeout=5000 This JDBC url is...

This tool is just a toy! Everything is hardcoded and difficult to change by end user... :-( An example of JDBC string to connect to AWS Aurora cluster (https://stackoverflow.com/questions/56403686/aurora-mysql-jdbc-fail-over) jdbc:mysql:replication://master.xxxx.rds.amazonaws.com:3306,read.xxxx.rds.amazonaws.com:3306/dbnamerhere?autoReconnect=true&logger=com.mysql.jdbc.log.Slf4JLogger&allowSlavesDownConnections=true&readFromMasterWhenNoSlaves=true&loadBalanceBlacklistTimeout=5000 This JDBC url is...

This tool is just a toy! Everything is hardcoded and difficult to change by end user... :-( An example of JDBC string to connect to AWS Aurora cluster (https://stackoverflow.com/questions/56403686/aurora-mysql-jdbc-fail-over) jdbc:mysql:replication://master.xxxx.rds.amazonaws.com:3306,read.xxxx.rds.amazonaws.com:3306/dbnamerhere?autoReconnect=true&logger=com.mysql.jdbc.log.Slf4JLogger&allowSlavesDownConnections=true&readFromMasterWhenNoSlaves=true&loadBalanceBlacklistTimeout=5000 This JDBC url is...