Sonsivri
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
March 26, 2019, 07:33:50 19:33


Login with username, password and session length


Pages: 1 2 3 4 5 6 [7] 8 9 10
 61 
 on: March 03, 2019, 05:01:40 05:01 
Started by HackAndCrack - Last post by HackAndCrack
Why my CofMaker post is not visible ?

I posted in Electronics > Softwares.


 62 
 on: March 02, 2019, 05:28:12 17:28 
Started by titi - Last post by towlerg
Sorry, figure of speech, all I meant to say was that I installed on top of an existing activated version, using the reg/patch/serial whatever.

 63 
 on: March 02, 2019, 10:21:55 10:21 
Started by titi - Last post by HackAndCrack
Mod. although this post is over 150 and my post is not a reply per se, it is related.

Installed latest, 3.1.2.1 ontop of previous patched version. Although titlebar shows trial and Buy PicBasic appears on toolbar, activation manager continues to show activated and everthing seems to run ok. Will advise if 15 day trial kicks in.

Why patch ? Keygen works fine. I just tested it. All devices are enabled.

 64 
 on: March 02, 2019, 08:12:53 08:12 
Started by titi - Last post by towlerg
Mod. although this post is over 150 and my post is not a reply per se, it is related.

Installed latest, 3.1.2.1 ontop of previous patched version. Although titlebar shows trial and Buy PicBasic appears on toolbar, activation manager continues to show activated and everthing seems to run ok. Will advise if 15 day trial kicks in.


Version history

    Fixed bit-compare and bank-select for banks higher than 15 in K42/K83 families
    Fixed compile error when using arrays with 10F3xx
    Fixed HPWM for 16F18313/23, 16F1769
    Changed default #CONFIG for 16(L)F15xxx family to set SOSC pins to normal I/O
    Changed default #CONFIG for 16(L)F171x family to disable ZCD on power up
    Fixed HPWM CCPTMRSx-selection for 18(L)FxxK42
    Fixed PPS and HPWM for 16F161x family
    Fixed missing SFRs in 18LFxxK42 devices







 65 
 on: March 01, 2019, 11:14:59 23:14 
Started by alichan - Last post by sam_des
I guess that depends on your compiler as well as Proteus.
See attached file, its for AVR generated by gcc. Preotus is v8.1 SP1.

sam_des

 66 
 on: March 01, 2019, 03:11:11 03:11 
Started by DreamCat - Last post by Xwing
More than anything they make it a question of national security, even if it were software for weapon systems or nuclear power plants.
I've sent a reminder email now, let's see what happens.

 67 
 on: March 01, 2019, 03:10:45 03:10 
Started by Just4Fun - Last post by Just4Fun
Hi,
this is a STM32 Arduino and a Cyclone II FPGA dev. board to start playing with softcores. It is also "Multicomp" compatible ("Multicomp" is a modular VHDL design to "run" some famous retro 8 bit CPUs made by Grant Searle) giving the option to "run" easily a VHDL SOC with a Z80/6809/6502 CPU and I/O.




The PCB allows to use a micro-SD too:



Here "The Thing" in action "running" a Multicomp Z80 with CP/M 2.2 as OS: https://youtu.be/j8qfqlEfJm8

All the details can be found here.

 68 
 on: February 28, 2019, 06:48:41 18:48 
Started by DreamCat - Last post by DreamCat
It seems like very very difficult to get software.  Sad

 69 
 on: February 28, 2019, 11:57:21 11:57 
Started by alichan - Last post by alichan
Thanks, but it's not useful. It doesn't have debugging symbols so I cannot see the variables when debugging (step-by-step) that is the annoying thing.




 70 
 on: February 28, 2019, 11:44:47 11:44 
Started by alichan - Last post by alichan
Hello.

Surely when debugging with Proteus you have noticed the message "Format (-1) not valid for type (0x00000000)" in CPU variables or watch windows. I looked in the documentation, general search on Internet but couldn't find anything.


Do you know why or the reasons this message appears with some variables ?

It happens mostly with anidated structs (C language), deferencing some pointers, bitfields, etc. but not with all of them. I cannot find the reason of such message, what pattern it follows since in some cases you can see variables correctly and not in others, or any documentation about it, and doesn't help to debug since you cannot see the variable contents (and I have enough with the apparent Proteus limitation to show 32-bit variables).

As workaround after some tries, I found that if you create a (global) pointer of same type of the variable you want to see, then assign the variable address to the pointer, even if the pointer is not used (use volatile to avoid the optimizer removing it), Proteus will show the correct variable contents in any variable of the same type, even not referenced. Creepy...

Example (forget syntactic correction in example, it's not relevant here):

struct ex1
{
   ...
}

struct EX2
{
   struct ex1 test;
   int test2;
} ex2;

If you expand ex2 while debugging, it will show "Format (-1) ...". Now if you

volatile struct EX2 test * debug_test = & ex2;

It will show correctly ex2 contents (but chances are not ex1, and you have to do the same with the inner struct).


I'm insterested on any experience you had with this... Cheers mates.

Pages: 1 2 3 4 5 6 [7] 8 9 10

DISCLAIMER
WE DONT HOST ANY ILLEGAL FILES ON THE SERVER
USE CONTACT US TO REPORT ILLEGAL FILES
ADMINISTRATORS CANNOT BE HELD RESPONSIBLE FOR USERS POSTS AND LINKS

... Copyright 2003-2999 Sonsivri.to ...
Powered by SMF 1.1.18 | SMF © 2006-2009, Simple Machines LLC | HarzeM Dilber MC