Any ideas what I can do to investigate?

Add a delay after each printf ...

The serial console buffer gets filled faster than it empties and it leads to a panic() condition because there is no more buffer space.

Cheers,

Sylvain

I got the same with c121. Apparently some dependencies of compal_dsp_dump target application was broken since this application was last updated. I hadn't time to pinpoint, what exactly was broken, but dsp dumping in version 4829...e844 works:

http://bb.osmocom.org/trac/browser/src?rev=48298d17fea548956c8fde2a1121c52f9...

Regards, André

On 12/03/11 15:44, Henk wrote:

Hi all,

I am trying to get a dump of the DSP code, but after 2 lines of hex the device seems to get stuck.

Some watchdog or so, missing something in the initialization sequence? According to the docs the cDSP ID seems to indicate a version B dsp...

Any ideas what I can do to investigate?

• Henk

./osmocon -p /dev/ttyS0 -m c123 ../../target/firmware/board/compal_e88/compal_dsp_dump.compalram.bin

Output: (I had commented the register locations to see if it helped...)

OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified)

Device ID code: 0xb4fb ==> CalypsoLite Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 ==> Version B Die ID code: 168f2c10cb001251 ====================================================================== Assert DSP into Reset Releasing DSP from Reset DSP bootloader version 0x0100 DSP dump: DROM [09000-0dfff] 09000 : 0006 0052 ff7d 009a ffc8 fd21 00b7 ffbf fef7 0009 ff2e fe97 0071 02ce 0719 03f2 09010 : 04be 0625 0359 0535 08e4 033b 0620 078d 02cd 07c5 089e 0346 0494 071f 02d1 03e8