Re: [uracoli-devel] Flash using WiBo, am I missing something?

[Tomás Glaria]

Ok, got the error.

I was using DEBUG = 1 on the WiBo in the node, that meant that for each received piece of firmware received, it sent some info through the UART which makes the whole system considerably slower.

Disabling that 'UART' worked for 57600 AND 500000.-

So, let' keep trying.

About the board abstraction, why is it so much work?

Which generated code?

I just modified the board_cfg.h file (adding my board), added the board_custom.h file in /inc/boards.

Then changed the makefile so it could be built.

What could have I missed?

I'm not interested in the whole uracoli environment, only in the bootloader, and since it's already implemented for some boards with the same mcu, I thought I needn't do any big change.

Am I wrong?

On Tue, Dec 23, 2014 at 1:02 PM, Axel Wachtler <address@hidden> wrote:

Hi Tomas, my first guess is, that nobody will have tried a 500kbps baudrate before. There is also no handshake and the air interface is 250kbps brutto rate, so maybe overflow is not handled. Can you give 57600bps a trial?

If i.r.c., short address 0 is the gateway, can you try a number that is not 0xffff and not 0x0 for -a

Next, try a regular binary with a standard hardware like sparkfun or radiofaro, stripping down hardware in the src-package is unecessarry complex - some files have generated code - too much work!

To have your own board abstraction, the devel package with scons is a better choice.

Good luck, Axel.


Am 23.12.2014 um 16:12 schrieb Tomás Glaria:

I'm using the uracoli-src-0.4.2.zip file from
http://uracoli.nongnu.org/download.html
I want to use the WiBo for ATmega128RFA1 on a board with no peripherals
(for testing, just the µC, radio and UART).
I made a board definition based on an existing board (BAT) but removing
the all the unused peripherals (LEDS, buttons).
I cand compile and load the WIBOhost application, which works
(apparently) and the WiBo (the bootloader) on one node.
I compiled also the xmpl code to test the wireless bootloader.

Using nodeaddr, I made an HEX file for the wibohost application and WiBo
+ Xmpl code:
For wibohost:
 > python nodeaddr.py -a 0x0000 -p 0xCADE -f ..\bin\wibohost.hex -c 11
-B bat_2 -o out_host_0000.hex
For WiBo + Xmpl:
 > python nodeaddr.py -a 0x0001 -p 0xCADE -b ..\bin\wibo.hex -f
..\bin\xmpl_wibo.hex -c 11 -B bat_2 -o out_xmpl_0001.hex

The fuse in the Host is programmed to boot from the app (BOOTRST
disabled), and the fuse in the node is programmed to boot from the
bootloader (BOOTRST enabled).
I can then communicate with the Host node using the wibohost.py file, I
can scan and find the node.
If I send the node to load the application, it works, and loads the
application (shows some debug infor on screen using UART).

Now, I try to wirelessly program the node. Using wibohost.py:
python.exe -v -P com3:500000 -A 1 -u ..\bin\xmpl_wibo.hex

The file is transfered, and the device is, apparently, flashed, but when
the bootloader jumps to the application, it hangs and does nothing (I
get no output on screen).

Am I missing something?
Maybe some offset for the app?

I'm using Windows 7, and flashing the bootloader using Atmel Studio 6.2.-

--
Atte.
Tomás Ángel Glaría López
Ing. de Estudios
CADETECH S.A.

--

Atte.

Tomás Ángel Glaría López

Ing. de Estudios

CADETECH S.A.