Show Posts - Sjaak

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - Sjaak

2266

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 12, 2010, 03:20:37 pm

Wasn't mend to offend anyone. Just take it with a little grain of salt (bad translation of a dutch saying

) (i love bad translations)

I like this kind of comments in sourcecode, but I didn't know what serial comma's were. Never too old

2267

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 12, 2010, 02:13:47 pm

What do you BTW mean with serial comma's?

I'm not a native speaker

and my english is prolly better then your dutch

Ok. I'll wait for the next release. How many room is there left for new code (using the new bootloader)?

2268

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 12, 2010, 01:26:35 pm

I also though of entering 'yes' or 'I agree' instead of hitting enter twice for the final version. I'm not satisfied with the javascript tool but I had to

I think it is not suitable for auto-building.. But it did the job

Good additions, although the debug define could be left out, but on the other hand why not..

I try to register an email with google code later on. (Shall i also add the other changes (other topic) in the trunk?

)

2269

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 12, 2010, 12:34:56 am

looks like I made some huge mistakes in my code :S The problem was a bad testpattern (not suitable for testing bleh!). I now used a .hex of the 217 svn and i noticed the error and (I think) I corrected it.

Anyway I included it (the bootloader of svn217') in the firmware.h.. I Also included an .html file (sorry no perl on this windows box) which convert the bootloader to an array which can be used in firmware.h. Select the start and up to the last full 16 byte line.

first line to be selected:

Code: [Select]

:105000002F8C20004227A9004507A90042A7AE0027

last line to be selected:

Code: [Select]

:1057E000FFFFFF00FFFFFF00FFFFFF00FFFFFF00C5

The .html should automagicly add the last 4 word together with the fuses. The .html also handles the byte to 'program word' conversion. I didn't saw a way to use objdump to dump the relevant parts...

As far as I know this attached package should now behave as expected, but I couldn't test it in real (stil haven't got a pic programmer). I also changed the commented out section to be correct byte to 'programword' conversion.

So Ian, could you please please test it? :p please alter the fwlocation to 0xA800 and uncoment the section in main.c

If it works correctly I'll rewrite the flash.s to comply with the creative 0 license (hadn't the time for it tonight!)

2270

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 11, 2010, 11:51:41 am

I could rewrite it so it is my 'own' code. The it should be ok to release it under the same license as the buspirate? It is all documented on microchip.com. I dunno if a couple of asmcodes BTW are covered/infected by the gpl.

Ferase(0xA000); should erase the second last page. I indeed forget the two instructions before the loader. I looked at the current code and the jump to userapp is located just before start??

I think the delay should stay as it is also used as communicationstimeout.

I'll try to come up with a script to export a .hex to the needed include.

2271

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 11, 2010, 10:21:31 am

Ian, I hope you understand what i did wrote

I tried to add as much comments (normally not my style

)

The byte order for the firmware.h should be the same order as the loader sends them. If it is convienant it could be changed easily (to support an auto-build process).

2272

Bus Pirate Support / Re: Concise List Of Differences Of V2.go and V3?

January 10, 2010, 02:06:52 pm

if you look in the svn, you can find the 'little' differences:

http://code.google.com/p/the-bus-pirate ... dwarev25.h

and

http://code.google.com/p/the-bus-pirate ... rdwarev3.h

Hardware2.5 is the BP v2.go and hardware3 is the latest version. They share the same source code and hardware (chipwise). The only difference is AFAIK the I/O pin placement. More details on http://dangerousprototypes.com/bus-pirate-manual/

Did I miss something here, Ian?

2273

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 09, 2010, 06:13:46 pm

No problem! Even got some more ideas to implement!

I forgot to mention is it lighting fast. Programming is done in a blink of an eye. So it is as safe as i can be...

2274

Bus Pirate Development / Re: Bootloader v4 (ds30 Loader)

January 09, 2010, 05:54:17 pm

I almost finished the installer, but I came to a point where it is not safe for me to further test it (writing the real bootloader to the correct location and alter the reset vector)

The current build writes a test pattern (from firmware.h) to a 'safe' location (0x9000). I saw it erases the page (or perhaps the other bootloader did it?) and write the test pattern correctly (read it back with the old bootloader). for the final build firmware.h should be altered with the correct firmware and load adress and the commented-out code should be enabled. And perhaps some bugs fixed

I already put it under the same license as the buspirate and gave credit for the pieces I did use (mostly from the buspirate project and some asm lines from the C30 loader).

everything should be in de archive.

2275

Bus Pirate Development / Bootloader v4 (ds30 Loader)

January 09, 2010, 01:22:41 pm

How about storing an recentfilex.xml in the archive?

2276

Bus Pirate Development / Bootloader v4 (ds30 Loader)

January 08, 2010, 10:09:41 am

It is difficult to explain, but i try anyway:

Code: [Select]


begin of page

A800 = 1010 1000 0000 0000
F800 = 1111 1000 0000 0000
       =================== &
A800 = 1010 1000 0000 0000 

end of page

ABFF = 1010 1011 1111 1111
F800 = 1111 1000 0000 0000
       =================== &
A800 = 1010 1000 0000 0000

This only matches the range we need.

If you and it with 0xA800 the following statemant is true:

Code: [Select]


8800 = 1000 1000 0000 0000
A800 = 1010 1000 0000 0000
       =================== &
8800 = 1000 1000 0000 0000

BTW you don;t receive an verification error if you fail silently (bra main), it never reaches the verify subs.

Not much snow here

besides when using a car it prevents you from falling

2277

Bus Pirate Development / Bootloader v4 (ds30 Loader)

January 08, 2010, 08:56:24 am

No thanks, like to help.

[quote author="ian"]
>mixed together with some UART and mode LED debugging. If I implement initialize() from main.c and BpInit() from base.c I should be OK?
[/quote]

This is for the installer. I need to initialize everything the same way as BP it is in HiZ-mode. To provide the users some visual feedback (like mode led on and some kind of progress bar on the terminal)

2278

Bus Pirate Development / Bootloader v4 (ds30 Loader)

January 07, 2010, 11:42:20 pm

Hmm, I spend an evening studying how to write to the flash. I think I can write an installer for the new bootloader. It turns out is it easier then I first though, but it took a while to realize this :S

I'll write it tomorrow night, but i need your help for testing?

It will do the following things:

- erase the last page
- write the new bootloader and config bits
- erase the second last page
- erase the first page
- write a jump to the new bootloader
- verify?
- reset?

mixed together with some UART and mode LED debugging. If I implement initialize() from main.c and BpInit() from base.c I should be OK?

BTW i tried to look at the check in the bootloader and came up with this (didn't check the syntax much but looks ok):

replace line 75 (svn r195):

Code: [Select]

	.equ	WADDR3,	W8

add this after line 319 (svn r195):

Code: [Select]

	mov W0, WADDR3

replace line 397 (svn r195) with this block

Code: [Select]

erase:	and	#0xF800, WADDR3
	sub	#0xA800, WADDR3
	bra	z, prot		; if true protect it	
	bra	nprot
prot:	clr	DOERASE		; clear DOERASE flag, just to be sure
	bra	Main		; fail silently 
nprot:	btss	DOERASE, #0

c-equivalent (I hope

Code: [Select]

if ((waddr3&0xF800)==0xA800)
{   DOERASE=0;
    goto Main;
}

I think this will prevent any erase of the last block and also prevent any write within this region. It fail silently (which doesn't upset the casual user, nor do I think during normal operation we encounter this, but better safe then sorry and it is a bad idea to have checks outside your control..) It is getting late so the possibility exist i miss something... *yawn*

2279

Bus Pirate Development / Bootloader v4 (ds30 Loader)

January 07, 2010, 05:02:49 pm

i have a note about the protocol at home. When i'm home i could post it here.

I think fail silently; you get then just a verify error afterwards. (wasn't that one of the things we wanted to avoid??) although by normal operations should not get here..

2280

Bus Pirate Development / Bootloader v4 (ds30 Loader)

January 07, 2010, 01:22:29 pm

Great!

Extra check don't hurt I guess, better safe then sorry. (Or write a good disclaimer!!). Also there is plenty of room.

The adresscheck could be around row 379 for erase and for writes around row 392.

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#	Time	Memory	Function	Location
1	0.0175	2453968	session_write_close ( )	...(null):0
2	0.0178	2585592	ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )	...(null):0
3	0.0178	2586368	Database_MySQL->query( )	.../DatabaseHandler.php:119
4	0.0729	2725128	Database_MySQL->error( )	.../Db-mysql.class.php:273