Re: [riot-devel] sha256

[Oleg Hahm]

Hey Paco!

On Fri, Dec 16, 2016 at 06:47:19PM +0100, Francisco Javier Acosta Padilla wrote:
> I’m trying the sha256 module on RIOT master and I just realised it returns
> always a different value… for now, I’m doing this:
> 
> 
> sha256_init();
> sha256_update(, (uint8_t*)firmware_bin, firmware_size);
> sha256_final(, metadata.hash);
> 
> To initialise and store the hash, according to the unittest which does very
> similar.
> 
> Am I doing something wrong?

Strange. At a first glance your code seems to be valid for me. Could you share
a pointer to your project? Is maybe first somehow corrupted or is metadata a
part of firmware_bin?

Cheers,
Oleg

-- 
DPRINTK("strange things happen ...\n");
linux-2.6.6/drivers/atm/eni.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] sha256

[Francisco Javier Acosta Padilla]

Hi RIOTers!

I’m trying the sha256 module on RIOT master and I just realised it returns 
always a different value… for now, I’m doing this:


sha256_init();
sha256_update(, (uint8_t*)firmware_bin, firmware_size);
sha256_final(, metadata.hash);

To initialise and store the hash, according to the unittest which does very 
similar.

Am I doing something wrong?

Thanks in advance!

Cheers,

-- 
Francisco Javier Acosta Padilla
Research Engineer at INRIA Saclay
INFINE Team___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] STM32l1xx Internal ADC Channels

[Francisco Molina]

Hi,

I have been working with the STM32L151RC uc and would like to read two of
it's internal ADC channels. The problem is RIOT present implementation por
the ADC only takes into account external ADC lines, witch means it require
a GPIO assignment. What would be the best way of implementing this? a new
function in the adc lib that doesn't need a GPIO assignment or implement
this a a CPU function since these internal ADC channels are used to get
internal voltage references and such. Best regards,

Francisco Molina
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Cortex M0 HardFault

[Joakim Nohlgård]

On a related note, I had some trouble with unexplained hard faults when I
built newlib using gcc-6.2, but I didn't have time to investigate further
at that time and I simply reinstalled newlib built with gcc-5.4 instead.

Best regards,
Joakim

On Dec 15, 2016 5:51 PM, "Kaspar Schleiser"  wrote:

> Hey,
>
> On 12/15/2016 05:32 PM, Baptiste Clenet wrote:
> > What could cause:
> > Stack pointer corrupted, reset to top of stack
> > l.238, vectors_cortexm.c
> > (then board is halted)
> >
> > Any program I flash on the samr21 goes directly to hard_fault_handler()
>
> Any program, e.g., also "tests/hello-world"?
>
> > Board dead or something missing?
>
> Which OS are you on, what toolchain?
> Do you have a second samr21-xpro to test the binary?
> Are you on a clean master checkout?
>
> Seriously, did you try a different USB cable?
>
> Kaspar
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel