osmocon and boot loader experience

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

Steve Markgraf steve at steve-m.de
Tue Jan 18 19:14:55 UTC 2011


Hi,

On 18.01.2011 16:17, Sylvain Munaut wrote:

> The bootloader serial routing is stupid as hell ... basically you have
> : (from memory but the idea is there)

Hm, I didn't know that it was that bad.

 From my experience the Calypso romloader handles the uart much better.

Just as an experiment: Here's a compiled binary, which does nothing more 
then starting the Calypso romloader:

http://www.steve-m.de/projects/osmocom/chainload_tiny.bin

------------------------------------------------------
	.globl _start

#define MEMIF_EXTRA_REG	0xfffffb10
#define BOOTROM_ENABLE	(1 << 8)

_start:
	ldr	r1, =0x000a0000
wait:
	subs	r1, r1, #1
	bne	wait

	ldr	r1, =MEMIF_EXTRA_REG
	ldr	r2, =BOOTROM_ENABLE
	strh	r2, [r1]
	ldr	pc, =0x0

------------------------------------------------------

If anyone wants to try if that works better when having serial issues:

$ ./osmocon -p /dev/ttyUSB0 -m c123 -c 
../../target/firmware/board/compal_e88/layer1.highram.bin chainload_tiny.bin

It works quite well here.

Regards,
Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: chainload_tiny.bin
Type: application/octet-stream
Size: 32 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/85cdc108/attachment.bin>


More information about the baseband-devel mailing list