Some minor improvements ;)

Topic: Some minor improvements ;) (Read 12504 times) previous topic - next topic

Re: Some minor improvements ;)

Reply #15 – January 16, 2010, 12:22:05 pm

I'm glad to

Anywayz back to the dvm patch

Leave the version 4.1 or 4.1a or ..?

(I'll leave it at 4.1 for now)

Re: Some minor improvements ;)

Reply #16 – January 16, 2010, 02:21:57 pm

Go ahead and apply the dvm patch to the current SVN version. Please update first because I just committed a few changes to the files for the bootloader jump. I don't increment the SVN number, but if you're welcome to if you like. I looked hard for an auto increment or date function I can use with the compiler to give each release a new version automatically but I didn't find anything.

Re: Some minor improvements ;)

Reply #17 – January 16, 2010, 02:37:42 pm

I noticed you are committing GRRRRR!!

Finally i slipped through!

I also added bpInit() before jumping to the bootloader (to set everything to HiZ (I guess)) dunno if it give sideeffects when flashing (perhaps if it is powering a peripheral drawing too much current it will fail on flashing)

A timestamp should be in de compiler I think, the problem is perhaps timezones although we together are safe

screenshot:

Code: [Select]

1-WIRE>D
VOLTMETER MODE
Press any key to exit
VOLTAGE PROBE: 0.00V
1-WIRE>W
POWER SUPPLIES ON
1-WIRE>D
VOLTMETER MODE
Press any key to exit
VOLTAGE PROBE: 3.33V
1-WIRE>

Now back to c0ding..

Re: Some minor improvements ;)

Reply #18 – January 16, 2010, 03:14:12 pm

Do you have any thoughts on the terminal text system?

I think the 'press any key to exit' or 'press space to exit' should be standardized and added to the reusable message system.

I also hate the way it takes so many changes to add a new reusable message, maybe it could be redone with pointers.

Code: [Select]

 
#define MESSAGE_TEXT "hello"

char message_t[]=MESSAGE_TXT;

struct _messages{
  &message_t,

}

I guess it still needs the separate defines to use them. The system is described at the top of baseUI.c.

Re: Some minor improvements ;)

Reply #19 – January 16, 2010, 04:05:46 pm

no ideas yet for the messaging systeem. except to sort it with lines that need a linefeed and with lines that don't need it. Write the ones without linefeed with bpWstring and the others with bpWline..

Why not use bpWline(STD_MSG_1)? or cant you print it directly because it is in progmem and not in datamem?

I did a simular trick with the bpWBR macro.. save about 300 bytes.

Re: Some minor improvements ;)

Reply #20 – January 16, 2010, 04:08:52 pm

I believe if we use bpWline(STD_MSG_1) then it will duplicate the string in program memory for every use. THe 24F isn't a ROM friendly as the PIC 12/16/18. Could be wrong.

Re: Some minor improvements ;)

Reply #21 – January 16, 2010, 04:25:55 pm

sounds logical.. it is some kind of macro indeed..

Re: Some minor improvements ;)

Reply #22 – January 25, 2010, 03:04:18 pm

I was thinking about a new feature: detect a short circuit in the voltage regulator. If it doesn't rise to a minimum level after power on, disable it, and print a report.

Re: Some minor improvements ;)

Reply #23 – January 25, 2010, 04:21:57 pm

Sounds ok. Why not integrate it (also) in the selftest? (and make it integral part of unboxing the buspirate

first run a selftest before do anything else)

Is there BTW a problem with voltageregulators?

Re: Some minor improvements ;)

Reply #24 – January 25, 2010, 04:28:54 pm

I want to catch the situations where I power up a circuit for the first time and there's a solder bridge that shorts the power supply until I get the voltage report or test it with a multimeter.

I think it might be nice if the Bus Pirate saw that and disabled the power supplies if, for example, the 3v3 regulator is not 3v0 250ms after power up. Maybe differentiate W/w if you have a heavy load with a long sag.

Re: Some minor improvements ;)

Reply #25 – January 25, 2010, 06:57:38 pm

3v0 under load sounds bad and (i guess) that means the project is drawing lots of current. Also aren't a lot of chip designed for Vcc +- 5%?

The specs of USB is max 500mA and for the regulator it is [s:]just 150[/s:] max 500mA. (normal usage of 150mA??) Als from the datasheet the time to stabilizezd output is 10ms@10uF. Is it protected from shortciruit BTW?

I think 3V30 should be at least 3V13 and 5V00 should be at least 4V75 after 50ms?

Re: Some minor improvements ;)

Reply #26 – March 01, 2010, 03:01:12 am

Sjaak -

Congrats on these enhancements; they are excellent. I'm a newbie to PICs and the BusPirate, so I dont have a compiler to build the updated source.

Is there any chance you could PM me a link to a HEX file which includes these changes? Or, is there already a place for this type of thing? Do the "dailies" include HEX files for us non-compiler folks? (I do 99% of my work on AVRs and really dont want to install another IDE/Compiler just for this, is possible.)

Thanks for any info you folks can share.

Cheers,
Rob.

Re: Some minor improvements ;)

Reply #27 – March 01, 2010, 09:05:50 am

Ozrobbo, the dvm patch and resolution-improvement of volt is already intgrated in the main release (since v4.0 I think). The pinout commando isn't since it takes up valuable space. The other improvements are waiting to be implemented (i'm a bit busy with a major rework on the buspirate core system, see also the newterm thread).

Re: Some minor improvements ;)

Reply #28 – November 19, 2010, 09:20:50 pm

[quote author="Sjaak"]
I made some small improvement to the 170 branch and I would like to share it with you guys

- backspace.patch deletes also the character instead of just going back one position.
- pinout.patch add a global trigger ( '$' ) to display the (current) pinout. I was getting tired of looking this up constantly. I used the colorscheme of the probe kit seeed is selling.
- dvm.patch add a global trigger ( 'D' ) (only works on an active mode) to constantly monitor the voltage on the ADC pin. Press any key to exit this mode. Perhaps it should move to a seperate module like the AUX pin?

I want to extent the voltmeasure to be more precise but it is sufficient for Vcc measurement

Please provide some feedback (please be gentle

)
[/quote]

Dear all,

I'm a new user to BP and still struggeling with the wealth of features this little device offers. The patch to show the cable colors is very good, but it does not seem to be implemented in my firmware?

1-WIRE>$
Command not used in this mode
1-WIRE>i
Bus Pirate v3 (Seeed Studio)
http://dangerousprototypes.com
Firmware v2.4-Seeed
DEVID:0x0447 REVID:0x3043 (B5)
*----------*
POWER SUPPLIES OFF
Voltage monitors: 5V: 0.0 | 3.3V: 0.0 | VPULLUP: 0.0 |
a/A/@ controls AUX pin
Open drain outputs (H=Hi-Z, L=GND)
Pull-up resistors OFF
Bitorder configuration not allowed
*----------*

Is "Firmware v2.4-Seeed" the current one? Or do I need to use the firmwares from dangerousprototypes.com? Is it safe to flash my version from seeedstudio.com with the regular firmware?

Or am I just using the wrong place to issue "$"? When can I use this command?

Thank you very much!

Re: Some minor improvements ;)

Reply #29 – November 19, 2010, 09:53:37 pm

Hi daubsi,

You seem to have an old version of the firmware, and you realy need to upgrade

the firmware is at 5.10 (with v6 knocking at the door) The directions to upgrade are here: http://dangerousprototypes.com/docs/V2_to_v4_upgrades

If you follow the steps precisely it should be a breez... Be aware that the pinout command is combined with the 'i' command and '$' is used to enter the bootloader. See more in the wiki about the available commands: http://dangerousprototypes.com/docs/Bus ... ions_guide

BTW thanks for bumping my old topic