memory map

[muromec]

qtopia4-ezx-map - Mobile Linux Development Community

[wyrm]

mtd0
CADDO_SECOND 0×00000000 0×00008000 0×00008000 no no yes

Please make this read-only. Leaving it writable is a terrible idea, if you change the first 32bits on this partition you will have a brick, recoverable only by JTAG.

[muromec]

hmmm... ok

[wyrm]

"bluetooth must contain mbtdload binary to initialize bluetooth chip"

Take a look at bcm2035-tool, its free software and can do the firmware upload to bcm2045 too. If you need help to extract the chip fw from mbtdload i can point you on how to do it.

Also, you dont need to patch the chip firmware for it to work, but AFAIK you will need the patches for it to work with bluetooth audio.

[muromec]

>Take a look at bcm2035-tool, its free software and can do the firmware upload to bcm2045 too.

so i need to cut fw from mbtdload, use bcm2045 to upload it and then use normal hciattach?

>If you need help to extract the chip fw from mbtdload i can point you on how to do it.

its ASCII hex-coded binary? starts from :0200000282007A

thanks, i`l try

[wyrm]

>Take a look at bcm2035-tool, its free software and can do the firmware upload to bcm2045 too.

so i need to cut fw from mbtdload, use bcm2045 to upload it and then use normal hciattach?

>If you need help to extract the chip fw from mbtdload i can point you on how to do it.

its ASCII hex-coded binary? starts from :0200000282007A

thanks, i`l try

bcm2035-tool does the attach for you, but i suggest you to remove this part of the code, and use normal hciattach. (at the time i wrote it there was no bcm2035 support on bluez hciattach).

Yes, the firmware patching protocol looks just like this. On a780 it was binary (not ascii encoded) on the 'dload' file tough. If its already ascii on 'mbtdload' it will be a lot easier

And the hciattach cmdline is a little big.. Dont abuse the fact that you can set any BDADDR
hciattach /dev/ttyS1 bcm2035 460800 flow 01:02:03:04:05:06

[fsjon]

So does this mean it will allow bluetooth support but no A2DP right??

[wyrm]

no. It means everything will be supported when its supported.

[fsjon]

I see, thanks wyrm! I assumed what I thought because I've read that bluetooth is supported yet A2DP is not, hence my newbie conclusion.

[wyrm]

np, a2dp will be supported at some point. its just that easier stuff gets support first