Promising. Thanks! I'll have to see if this works with my digital signal (which cycles a lot faster than 35Hz), but this would simplify some code.mhoyt wrote:Code: Select all
static vudword t1, t2; ...
Search found 32 matches
- Fri Apr 27, 2012 11:08 am
- Forum: NetBurner Software
- Topic: Help with non-maskable interrupt
- Replies: 6
- Views: 5719
Re: Help with non-maskable interrupt
- Fri Apr 27, 2012 10:02 am
- Forum: NetBurner Software
- Topic: Help with non-maskable interrupt
- Replies: 6
- Views: 5719
Re: Help with non-maskable interrupt
>Is this for a weather station product or a home project? If a home project, maybe use an external 1-wire peripheral to offload some of the issues? Home project, but I'm trying to keep costs down by doing as much in software as possible. (That made more sense before I realized how hard it is to get ...
- Fri Apr 27, 2012 8:00 am
- Forum: NetBurner Software
- Topic: Help with non-maskable interrupt
- Replies: 6
- Views: 5719
Help with non-maskable interrupt
Yes, me again. I've run into yet another snag getting one wire working. It involves the timing of interrupt handling. If you're willing to help, please bear with some explanation: The project is a weather station, with a handful of devices using one wire, and some digital inputs I'm tying to IRQs. T...
- Fri Apr 27, 2012 7:00 am
- Forum: NetBurner Software
- Topic: Bit banging one wire protocol - help needed
- Replies: 7
- Views: 6342
Re: Bit banging one wire protocol - help needed
J2[41] is working much better for me. Thanks!
- Wed Apr 25, 2012 5:18 pm
- Forum: NetBurner Software
- Topic: Bit banging one wire protocol - help needed
- Replies: 7
- Views: 6342
Re: Bit banging one wire protocol - help needed
The Dev70 boards have a 1K pulldown to ground associated with the Dipswitches. Bingo. I'm on a dev70 board, and it never occurred to me to even look at the dip switches. And there's the 1k pulldown. Mystery solved. Alright. The only reason I'm sticking the 5270 into the dev70 board, is because the ...
- Wed Apr 25, 2012 10:36 am
- Forum: NetBurner Software
- Topic: Bit banging one wire protocol - help needed
- Replies: 7
- Views: 6342
Re: Bit banging one wire protocol - help needed
Scott, That doesn't make sense. What pins are you using? Are they associated with LEDs or other function on the Dev board? How are you addressing the pins? I have used 10k pull-ups on many lines without even thinking about it and never had a problem. Ed It absolutely doesn't make sense, which is wh...
- Wed Apr 25, 2012 5:40 am
- Forum: NetBurner Hardware
- Topic: Unexpected GPIO behaviour; reading 0 where 1 expected
- Replies: 4
- Views: 4045
Re: Unexpected GPIO behaviour; reading 0 where 1 expected
C'mon, folk. Someone here must have detailed knowledge of how these GPIO pins work. I've never used a processor where you had to drag a pin high this hard, to get it to register a logic 1, which makes me think I've done something wrong...
- Wed Apr 25, 2012 5:36 am
- Forum: NetBurner Software
- Topic: Apparent compiler bug involving volatile
- Replies: 8
- Views: 4893
Re: Apparent compiler bug involving volatile
OK I understand better now. I don't see why it wouldn't work although I must admit when I want to communicate this way between an interrupt and a task I use an OS facility like OSSemPend/OSSemPost. Using a shared resource without some sort of mutual exclusion technique can be fraught with peril, al...
- Wed Apr 25, 2012 5:26 am
- Forum: NetBurner Software
- Topic: Noob question about creating threads
- Replies: 15
- Views: 10478
Re: Noob question about creating threads
My question is can I set this up so it runs independent of the TCP function? I'd like the TCP function and the GPIO functions to be able to run simultaneously so the only delay created in the TCP function by the GPIO functions is caused simply by resource use. Yes, your main application look just r...
- Tue Apr 24, 2012 10:38 pm
- Forum: NetBurner Software
- Topic: Apparent compiler bug involving volatile
- Replies: 8
- Views: 4893
Re: Apparent compiler bug involving volatile
It's hard to know exactly what you are trying to achieve here without more of your code but this appears to me to be highly unlikely to work and it has nothing to do with volatile. ++ppi is not incrementing the value of the integer, it's incrementing the value of the pointer to the pointer. So now ...