I purchased another ESP8266 module early this year and it behaved completely different to previous one :shock:
The new one had software 0.25.0.0 and the old 0.17.09.01.
AT+GMR
AT version:0.25.0.0(Jun 5 2015 16:27:16)
SDK version:1.1.1
Ai-Thinker Technology Co. Ltd.
If you type AT+CIFSR you get a list of IP's and MACs for acess point and client if you have both enabled.
+CIFSR:APIP,"192.168.4.1"
+CIFSR:APMAC,"1a:fe:34:e6:2d:20"
+CIFSR:STAIP,"0.0.0.0"
+CIFSR:STAMAC,"18:fe:34:e6:2d:20"
On the up side 0.25.0.0 seems to be more stable then the 0.17.09.01 one...
Nick.
↧
Share your working BASCOM-AVR code here : Thingspeak field update example : REPLY
↧
BASCOM-AVR : ATTiny4313/ Interrupt : NEWTOPIC
Hi,
I'm faced with a nasty problem.
During simulation the courser jumps on the second Interrupt (INT=0) not to loop instead it jumps to config powermode= Powerdown. I know this problem from teh past and so I used ">=" but this time I need it correctly.
This effect Ive on two machines (laptop and PC/ Win7/ IDE 2.0.7.8/ 003).
If I try this program on chips they simple react on each interrupt.
What is wrong with the program?
Best regards,
'Test02
'----------------------------
$regfile = "attiny4313.dat"
$crystal = 8000000
$hwstack = 64
$swstack = 64
$framesize = 64
'$sim
'--------------------------
Dim T As Byte, Sol01 as Byte
T = 5
'----------------------------
Ddrb = &B00000001
Ddrd = &B00000000
Portd.2 = 1
'----------------------------
On INT0 Ontick01
Config INT0=LOW_LEVEL
Enable INT0
Enable interrupts
'----------------------------
Do
If Sol01 = 3 Then
Gosub Ontick
Sol01 = 0
End If
Config Powermode=PowerDown
Loop
'----------------------------
Ontick:
Portb = &B00000001
Waitms T
Portb = &B00000000
Return
'----------------------------
Ontick01:
Incr Sol01
Return
'----------------------------
End
[b:86eb85bfda][color=red:86eb85bfda](BASCOM-AVR version : 2.0.7.8 )[/b:86eb85bfda][/color:86eb85bfda]
↧
↧
Various : XTEA Problems : REPLY
Hello,
i just want to use the "new" lib "XTEA2.lib" wich comes with the latest version of Bascom (2.0.7.9).
When i use "Xteaencode Msg(1) , Key(1) , 16" the compiler will still use the "old" version "XTEA.lib"
So how can I use or how do i have to call the "XTEA2.lib"?
Thanks in advance, dani
[quote:657e63b13d="techknight"]I know this is old, But I ran into a similar problem. The problem is with Big-Endian vs Little-Endian. its different between high-level and low-level systems. There is a library XTEA2 which fixed it, based upon my requests.[/quote:657e63b13d]
↧
Various : XTEA Problems : REPLY
OK, at least i figured it out ...
I simply had to put $lib "xtea2.lib" at the code.
[quote:157fbec3fb="danielle"]Hello,
i just want to use the "new" lib "XTEA2.lib" wich comes with the latest version of Bascom (2.0.7.9).
When i use "Xteaencode Msg(1) , Key(1) , 16" the compiler will still use the "old" version "XTEA.lib"
So how can I use or how do i have to call the "XTEA2.lib"?
Thanks in advance, dani
[quote:157fbec3fb="techknight"]I know this is old, But I ran into a similar problem. The problem is with Big-Endian vs Little-Endian. its different between high-level and low-level systems. There is a library XTEA2 which fixed it, based upon my requests.[/quote:157fbec3fb][/quote:157fbec3fb]
↧
BASCOM-AVR : ATTiny4313/ Interrupt : REPLY
[quote:ba3d3cc5ae="2New"]During simulation the courser jumps on the second Interrupt (INT=0) not to loop instead it jumps to config powermode= Powerdown. [/quote:ba3d3cc5ae]
If you've used "run program", instead of single step modes, this is the correct behavior.
[quote:ba3d3cc5ae]What is wrong with the program?[/quote:ba3d3cc5ae]
I'd say it is ok, rather it's wrong understanding about the simulator's howto's.
↧
↧
BASCOM-AVR : ATTiny4313/ Interrupt : REPLY
When deactivating Powerdown the simulation runs perfect the same under "run program".
Problems occour under single step and on the chip.
I tried to find out whether the Flags have an influence to the result:
Single step shows I/H/S/N/C (powerdown) and H/C (return)
Run program show I/H/C (powerdown and return)
Does this information helps?
↧
BASCOM-AVR : ATTiny4313/ Interrupt : REPLY
Assuming the problems are much more deeper.
Tried just to add "Print Sol01" and I got strange error messages.
Error : 222 Line : 41 Illegal character [expected (, got '' [_PRDWORD]] , in File : F:BASCOM-AVRTestsTesttest03.bas
Error : 222 Line : -218 Illegal character [expected (, got '' [_PRDWORD]] , in File : C:PROGRAM FILESMCS ELECTRONICSBASCOM-AVRLIBMCS.LBX
Will try a new istallation.........again and again.
↧
BASCOM-AVR : ATTiny4313/ Interrupt : REPLY
I've installed IDE-Version 2.0.7.9. 003 and the problems are still there. The installation of some print routines shows a difference between the number of "ISR"and "Do...Loops".
Am I the only one faced with this effect?
↧
BASCOM-AVR : ATTiny4313/ Interrupt : REPLY
[quote:4b35aae453="2New"]Problems occour under single step and on the chip.[/quote:4b35aae453]
It works in simulation, as I would expect.
Your code in contrary may not work as you expect.
It may be that you don't understand how "Low Level" works. In this mode the interrupt triggers as long as the pin is pulled low (and in the same repeatedly wakes up the controller), so the variable counts till 3 in a few microseconds.
That means as well it simulates ok, your code doesn't make any sense on a real chip.
But your complaint was about the simulation, right?
↧
↧
BASCOM-AVR : ATTiny4313/ Interrupt : REPLY
Sure, I have tried Fallig with the same result.
Even with Low Level all the signals are clear and stable, I have watch them on an Logic analliser.
I reinstalled the program on a second machine.... same outcome.
↧
BASCOM-AVR : Xmega256D3 and TWIE compilation error : REPLY
Unfortunately in all early XM...D3 chips TWIE was not available at all, see the datasheet Errata section. That's why it's not in the .dat files yet. Only the latest revision of the chips should have a proper working TWIE. If the register "Mcu_revid" of the chip reads a value lower than 8 there is no working TWIE.
↧
BASCOM-AVR : Xmega256D3 and TWIE compilation error : REPLY
[quote:725adfcbef="holli"]Unfortunately in all early XM...D3 chips TWIE was not available at all, see the datasheet Errata section. That's why it's not in the .dat files yet. Only the latest revision of the chips should have a proper working TWIE. If the register "Mcu_revid" of the chip reads a value lower than 8 there is no working TWIE.[/quote:725adfcbef]
Thanks Holli. I just discovered that mention of the need for having a > rev 7 processor in the help example. Mine identified as just a revision 4, so indeed i'm out of luck there..
I did a quick attempt at getting a software based solution going, but i still see no action on the ports at the moment. In the attempt i added I2C.LIB; not sure if that's possible in combination with the xmega.lib? I suppose they both define the same I2C commands?
Or... ow, wait, i'll have to revert to the original definition file for the processor. Maybe it's now automatically assuming it's hardware ready. I'll try that first thing tomorrow.
Thanks again Holli.
↧
BASCOM-ARDUINO : Arduino Nano with I2c LCD and backlight : REPLY
Ben
I have been having trouble with this sometimes it worked then not.
Well I found it if I do not start with "home" I get problems
Regards Paul
↧
↧
BASCOM-ARDUINO : Arduino Nano with I2c LCD and backlight : REPLY
Paul
Thanks for your reply. So home should be used.
Have fun
Ben Zijlstra
↧
BASCOM-AVR : Variable gets zeroed out after Lookupstr : NEWTOPIC
Here's my sample code. I'm trying to create a lookup table. The variable LocalIndex keeps getting set back to zero. I'm sure I'm missing something, but I've been scratching my head for a while.
Thanks!
[quote:006065c7d9]
$regfile = "usb1286.dat"
'$crystal = 4000000 ' used crystal frequency
$baud = 19200 ' use baud rate
'$hwstack = 30 ' default use 32 for the hardware stack
'$swstack = 30 ' default use 10 for the SW stack
'$framesize = 30 ' default use 40 for the frame space
Dim CharacterToLookUp as String * 1
Dim CompareString1 as String * 1
Dim LocalIndex as Byte
Dim Junka as word ' Junk for testing
Dim Junkb as string * 1' Junk for testing
Declare Function LookupCodes(CharacterToLookUp as String * 1) as Word
''''''''''''''''''''''''''''''''''''
Junkb = "A"
Junka = LookupCodes(Junkb)
end
''''''''''''''''''''''''''''
Function LookupCodes(CharacterToLookUp as String) as Word
LocalIndex = 0
Do
Print "Local Index BEFORE Lookupstr is " ; LocalIndex
CompareString1 = Lookupstr(LocalIndex, MainData) ' ******* THE PROBLEM SEEMS TO BE HERE
Print "Local Index AFTER Lookupstr is " ; LocalIndex
Print " CompareString1 is " ; CompareString1
Print ""
LocalIndex = LocalIndex + 2
Loop
End Function
MainData:
DATA "U" , 21
DATA "V" , 22
DATA "W" , 23
DATA "X" , 24
DATA "Y" , 25
DATA "Z" , 26
[/quote:006065c7d9]
[b:006065c7d9][color=red:006065c7d9](BASCOM-AVR version : 2.0.7.8 )[/b:006065c7d9][/color:006065c7d9]
↧
BASCOM-AVR Old versions : Variable gets zeroed out after Lookupstr : REPLY
it appears to be a bug. I will check it. Might have to do with the short string.
↧
BASCOM-AVR Old versions : Variable gets zeroed out after Lookupstr : REPLY
the problem is your DATA table. for a string lookup, there should only be strings in the table. but you have bytes too.
↧
↧
BASCOM-AVR Old versions : Variable gets zeroed out after Lookupstr : REPLY
Thanks for the response.
Is there a way to mix types in the DATA statements? If I have a Byte and a String, can I just read a Byte and a string? Or do all DATA statements need to be of the same type?
I'm guessing the solution is to either store the string as an ASCII code, or have two DATA tables for each type?
On a somewhat related subject, I'm guessing the answer is no, but can simple functions be done in DATA statements? For example, to make things easier to read:
DATA ASC("A"), ASC("B")
DATA 23 OR &B00001000, 25 OR &B00000100
Thanks!
↧
BASCOM-AVR : ATTiny4313/ Interrupt : REPLY
I feel it hard to understand what you write, you better specify what exactly does not work and what you want to achieve.
So you want to divide a signal by 3, but, as I wrote the low level mode for Int0 is utter nonsense.
And as this is obvious to me but obviously not to you, I have to assume, that you have still more problems to understand how software and controller works.
Also it's not much fun to answer your questions while your response is not detailed.
Let's have another try, after that I will stop responding:
1) Describe exactly, what you want to achieve.
2) Show or describe the frequency, shape and duty cycle of the signal, which should trigger the interrupt.
3) Show the code, which you've wrote for "falling".
↧
BASCOM-AVR Old versions : Variable gets zeroed out after Lookupstr : REPLY
you can mix different types, but a function like lookupstr expects only string data.
you could write your own function when you mix data types.
in 2080 you can do : data asc("A") , asc("b"), &B11 or 4
But with one restriction : the result will be byte data.
↧