Metrologia Industrial | Curso Pós-Laboral

2018-03-02 Thread Cenertec - Centro de Energia e Tecnologia 



versão web


Exmos Senhores 
 
Venho lembrar que o Curso METROLOGIA INDUSTRIAL, que terá lugar no Hotel 
Holiday Inn, em Gaia, é já nos próximos dias 10 (09:00-13:00) e 16 
(18:30-22:30) de Março, sendo a Formadora a Engª Maria João Mortágua, 
reconhecida Especialista neste tema. 
 
 
OBJETIVOS
No final do Curso todos os Participantes serão capazes de: 
 

Saber o que é a metrologia e a sua implicação em normativas da qualidade

 

Identificar e distinguir a visão nos quatro pilares industriais (ENG, QAS, 
MAN, PRD)

 

Saber identificar necessidades de compra de equipamentos conhecendo a 
implicação a nível metrológico

 

Identificar a necessidade de calibração de equipamentos

 

Ser capaz de distinguir calibração de validação

 

Saber interpretar um certificado de calibração e todos os dados implícitos 
ao mesmo (incertezas, erros, tolerâncias)

 

Saber gerir equipamentos e as suas calibrações

 

Conseguir identificar e definir periodicidades de calibração mediante um 
critério lógico e perfeitamente justificável

 
 
 
 
Programa e Inscrição on-line
 
 
Muito obrigada!
 
 
Cumprimentos, Raquel
Tlm: 91 488 64 39
 
__
Raquel Reis (PhD)
Diretora Geral 
Cenertec-Centro de Energia e Tecnologia
 
Rua Gago Coutinho, 185-187
4435-034 Rio Tinto / Portugal
 
Tel:  22 973 46 24 / 22 973 0747
Fax: 22 973 07 46
 
36 anos ao serviço da formação  
 
 
 
O presente e-mail destina-se única e exclusivamente a informar potenciais 
clientes e não pode ser considerado SPAM. 
Caso não pretenda receber informações clicar aqui. 
Esta mensagem é enviada sob a nova legislação sobre correio Electrónico, art. 
22.º do Decreto-lei n.º 7/2004, de 7 de 
Janeiro sobre correio electrónico não requisitado. Um e-mail não poderá ser 
considerado SPAM quando inclui uma forma de ser removido. 
Se não pretender receber a nossa newsletter clique aqui clicar aqui. 
Ao abrigo da Lei 67/98 de 26 de Outubro, de regulação do tratamento 
automatizado de dados de carácter pessoal, o utilizador poderá 
cancelar os mesmos, conforme disposto nos artigos 10º e 11º. Qualquer 
solicitação nesse sentido deverá ser feita pelo endereço 
do remetente. De salientar que, se pretende anular o seu e-mail, deve efetuar 
essa anulação pelo endereço de e-mail que se encontra 
registado na nossa base de dados, de outra forma ficaremos impossibilitados de 
o eliminar.



 | EvtKey versão 3.0.0.0 | Licenciado a CENERTEC   | Desenhado e 
Desenvolvido por EventKey | Copyright 2015 Cenertec

Re: Armel: Debian installer freeezes (GuruPlug Server plus)

2018-03-02 Thread Kari Tanninen 

"In Debian installer, for the various plug devices, we append to
the DTB at the end of the kernel rather than loading it separately."


Is that possible/reasonable?

U-boot have to link all files on boot and it is impossibe to append 
command line parametres to fdt-blob
without resize fdt-blob at U-boot. U-boot is using physical addressing 
only(?) and I think kernel cannot
resize itself before boot without relocation problems -> bootm_size 
variable issue.


If fdt is used, kernel should discard ATAG-variables by default, I 
think.


I suppose fdt-mechanism is meant to set HW-structure to both bootloader 
and kernel and U-boot is
allowed to modify "choosen" field for appending command line parametres 
before kernel boot.





Martin Michlmayr kirjoitti 1.3.2018 15:11:

(Adding Ian Campbell.)

Ok, I didn't notice the version of u-boot from the log you posted and
went on what you wrote.

However, looking at the log file again, I notice you're loading the
DTB file separately.

You say you follow my installation instructions but clearly you're
not.  In Debian installer, for the various plug devices, we append to
the DTB at the end of the kernel rather than loading it separately.

Can you please follow the instructions at
https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ and post
the output of that?



* Kari Tanninen  [2018-03-01 15:01]:
I'm using Debian stretch U-boot version (U-boot version number is 
visible on

the log-file). I have tried Debian "buster" U-boot version too, but it
freezes at "Setting egiga0" point. There is warning on "Debian Armel
installation guide", that U-boot does update kernel variables only on 
fresh
installation, if first U-boot version is older than 2014, there will 
be

problems becouse of "bootm_size" variable is missing and default value
cannot be set.

Flattened device tree -mechanism is not using those "ATAG" global
kernel/U-boot -variables, but problem is missing U-boot "boot_args"
-variable, too.

Fdt-file includes that "Chosen" -field for command line parameters and
U-boot has a commands to resize fdt -file and append command line 
parameters

to it before actual boot.

U-boot sets and can read correctly that fdt-file "chosen" part. U-boot
kprint line for that "chosen" value is visible on log-file.

Martin Michlmayr kirjoitti 1.3.2018 14:02:
> * Kari Tanninen  [2018-03-01 11:26]:
> > HW: Guruplug Server plus with JTAG-box (ARMv5-family)
> > original U-boot pre-2014
> ...
> > Is there any fix-up/work-aroud trick available or is new kernel
> > compiling
> > only option?
>
> I've never had a GuruPlug so I cannot really comment but why are you
> using the pre-2014 u-boot version?  I cannot remember all the
> differences of the u-boot versions of the installation page says you
> should upgrade your u-boot before installing Debian.  Maybe you can
> give this a try.
>
> Based on the logs you posted, it seems to me that the kernel and
> ramdisk are loaded but the kernel doesn't see the ramdisk, leading to
> the "no root" issue.

Re: Armel: Debian installer freeezes (GuruPlug Server plus)

2018-03-02 Thread Kari Tanninen 
NOTICE! Globalscale has bought at least two chunks of MAC-addresses, 
this unit MAC's starts as F0:AD:*



Kari Tanninen

### Minicom terminal 
output 

=> printenv
baudrate=115200
bootargs=console=ttyS0, 115200n8 earlyprintk 
base-installer/initramfs-tools/driver-policy=most
bootargs_console=console=ttyS0, 115200 root=/dev/sdb2 rootdelay=10 
base-installer/initramfs-tools/driver-policy=most
bootcmd=setenv bootargs ${bootargs_console}; run bootcmd_usb; run 
bootcmd_fdt; bootm 0x0080 0x0110 0x0c00;
bootcmd_fdt=fdt addr 0x0c00; fdt resize; fdt chosen; fdt list 
/chosen;
bootcmd_usb=usb start; usb start; ext2load usb 2:1 0x0080 /uImage; 
ext2load usb 2:1 0x0110 /uInitrd; ext2load usb 2:1 0x0c00 /guru

bootdelay=6
eth1addr=F0:AD:4A:00:47:00
ethact=egiga0
ethaddr=F0:AD:4A:00:46:FF
fdt_addr_r=0x0c00
fdt_high=0x
fdtaddr=c00
fileaddr=110
filesize=b2c4af
initrd_high=0x
ipaddr=10.4.50.6
kernel_addr_r=0x0080
ramdisk_addr_r=0x0110
serverip=10.4.50.5
stderr=serial
stdin=serial
stdout=serial

Environment size: 933/131068 bytes
=> tftp 0x0080 uImage
Using egiga0 device
TFTP from server 10.4.50.5; our IP address is 10.4.50.6
Filename 'uImage'.
Load address: 0x80
Loading: 
#

 #
 ###
 4.1 MiB/s
done
Bytes transferred = 2060842 (1f722a hex)
=> tftp 0x0110 uInitrd
Using egiga0 device
TFTP from server 10.4.50.5; our IP address is 10.4.50.6
Filename 'uInitrd'.
Load address: 0x110
Loading: 
*#

 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 ###
 4 MiB/s
done
Bytes transferred = 11715759 (b2c4af hex)
=> bootm 0x0080 0x0110
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   Debian kernel
   Created:  2017-12-05  16:25:07 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:2060778 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 0110 ...
   Image Name:   debian-installer ramdisk
   Created:  2017-12-05  16:25:07 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:11715695 Bytes = 11.2 MiB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.0-4-marvell 
(debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 
6.3.0-18) ) #1 Debian 4.9.65-3 (2017-12-03)
[0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), 
cr=0005397f

[0.00] CPU: VIVT data cache, VIVT instruction cache
[0.00] OF: fdt:Machine model: Globalscale Technologies Guruplug 
Server Plus

[0.00] bootconsole [earlycon0] enabled
[0.00] Memory policy: Data cache writeback
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 130048
[0.00] Kernel command line: console=ttyS0, 115200n8 earlyprintk 
base-installer/initramfs-tools/driver-policy=most

[0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 
bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 
bytes)
[0.00] Memory: 502240K/524288K available (3778K kernel code, 
395K rwdata, 1128K rodata, 296K init, 249K bss, 22048K reserved, 0K 
cma-reserved, 0K highmem)

[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xe080 - 0xff80   ( 496 MB)
[0.00] lowmem  : 0xc000 - 0xe000   ( 512 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)

Bug#891857: busybox: Special case for /32 subnets not working as expected

2018-03-02 Thread Benjamin Drung 
On Thu, 01 Mar 2018 17:55:52 +0100 Yuval Freund  
wrote:
> A fix for /32 has already been implemented in an earlier version of
> busybox, but it doesn't seem to work as expected, because the interface
> isn't defined while adding the relevant route.

To be more precise: The ip command will fail if the device is not
specified:

~# ip -4 route add default via 157.97.106.1 onlink
ip: RTNETLINK answers: No such device
~# ip -4 route add default via 157.97.106.1 dev eth0 onlink
~#

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg

Processed: busybox: Special case for /32 subnets not working as expected

2018-03-02 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> found 891857 1:1.22.0-19
Bug #891857 [busybox] busybox: Special case for /32 subnets not working as 
expected
Marked as found in versions busybox/1:1.22.0-19.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
891857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Armel: Debian installer freeezes (GuruPlug Server plus)

2018-03-02 Thread Martin Michlmayr 
Can you try:

tftpboot 0x0080 uImage
tftpboot 0x0110 uInitrd
setenv bootargs console=ttyS0,115200n8 earlyprintk 
base-installer/initramfs-tools/driver-policy=most
bootm 0x0080 0x0110


* Kari Tanninen  [2018-03-02 11:42]:
> Minicom terminal log Armel strech d-i:
> 
> bootm_size is currently not set, different values is tried when
> fdt_high/initrd_high not set:
> 
> bootm_size=512M
> bootm_size=0x1fb0
> etc.
> 
> (U-boot docs are pretty unclear with exact syntax for "hex" format)
> 
> -- Guruplug memories at fdt-blob
> -
> memory {
>   device_type = "memory";
>   reg = <0x 0x2000>;
>   };
> 
> 
>  {
>   status = "okay";
> 
>   partition@0 {
>   label = "u-boot";
>   reg = <0x 0x0010>;
>   read-only;
>   };
> 
>   partition@10 {
>   label = "uImage";
>   reg = <0x0010 0x0040>;
>   };
> 
>   partition@50 {
>   label = "data";
>   reg = <0x0050 0x1fb0>;
>   };
> };
> 
> KariTanninen
> 
> 
>  Minicom Terminal log
> #
> Welcome to minicom 2.3
> 
> OPTIONS: [18n
> Compiled on Feb 26 2009, 00:28:35.
> Port /dev/ttyUSB0
> 
>  Press CTRL-A Z for help on special keys
> 
> 
> => printenv
> baudrate=115200
> bootargs=console=ttyS0, 115200n8
> base-installer/initramfs-tools/driver-policy=most
> bootargs_console=console=ttyS0, 115200 root=/dev/sdb2 rootdelay=10
> base-installer/initramfs-tools/driver-policy=most
> bootcmd=setenv bootargs ${bootargs_console}; run bootcmd_usb; run
> bootcmd_fdt; bootm 0x0080 0x0110 0x0c00;
> bootcmd_fdt=fdt addr 0x0c00; fdt resize; fdt chosen; fdt list /chosen;
> bootcmd_usb=usb start; usb start; ext2load usb 2:1 0x0080 /uImage;
> ext2load usb 2:1 0x0110 /uInitrd; ext2load usb 2:1 0x0c00 /guru
> bootdelay=6
> eth1addr=F0:AD:4A:00:47:00
> ethact=egiga0
> ethaddr=F0:AD:4A:00:46:FF
> fdt_addr_r=0x0c00
> fdt_high=0x
> fdtaddr=c00
> fileaddr=110
> filesize=b2c4af
> initrd_high=0x
> ipaddr=10.4.50.6
> kernel_addr_r=0x0080
> ramdisk_addr_r=0x0110
> serverip=10.4.50.5
> stderr=serial
> stdin=serial
> stdout=serial
> 
> Environment size: 921/131068 bytes
> => tftpboot 0x0080 uImage
> Using egiga0 device
> TFTP from server 10.4.50.5; our IP address is 10.4.50.6
> Filename 'uImage'.
> Load address: 0x80
> Loading: #
> #
>  ###
>  4 MiB/s
> done
> Bytes transferred = 2060842 (1f722a hex)
> Using egiga0 device
> TFTP from server 10.4.50.5; our IP address is 10.4.50.6
> Filename 'uInitrd'.
> Load address: 0x110
> Loading: #
> #
> #
> #
> #
> #
> #
> #
> #
> #
> #
> #
>  ###
>  3.9 MiB/s
> done
> Bytes transferred = 11715759 (b2c4af hex)
> bootm 0x0080 0x0110
> ## Booting kernel from Legacy Image at 0080 ...
>Image Name:   Debian kernel
>Created:  2017-12-05  16:25:07 UTC
>Image Type:   ARM Linux Kernel Image (uncompressed)
>Data Size:2060778 Bytes = 2 MiB
>Load Address: 8000
>Entry Point:  8000
>Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at 0110 ...
>Image Name:   debian-installer ramdisk
>Created:  2017-12-05  16:25:07 UTC
>Image Type:   ARM Linux RAMDisk Image (gzip compressed)
>Data Size:11715695 Bytes = 11.2 MiB
>Load Address: 
>Entry Point:  
>Verifying Checksum ... OK
>Loading Kernel Image ... OK
> Starting kernel ...
> Uncompressing Linux... done, booting the kernel.
> 
> 
> 
> 
> 
> Kari Tanninen kirjoitti 1.3.2018 20:01:
> > I try tomorrow record Debian "Stretch" U-boot/uImage/uInitrd -terminal
> > output with instructions
> > "https://www.cyrius.com/debian/kirkwood/sheevaplug/install/;
> > 
> > Sorry delay, I have to load new binaries to GuruPlug and I'm not very

Re: Armel: Debian installer freeezes (GuruPlug Server plus)

2018-03-02 Thread Kari Tanninen 

Minicom terminal log Armel strech d-i:

bootm_size is currently not set, different values is tried when 
fdt_high/initrd_high not set:


bootm_size=512M
bootm_size=0x1fb0
etc.

(U-boot docs are pretty unclear with exact syntax for "hex" format)

-- Guruplug memories at fdt-blob 
-

memory {
device_type = "memory";
reg = <0x 0x2000>;
};


 {
status = "okay";

partition@0 {
label = "u-boot";
reg = <0x 0x0010>;
read-only;
};

partition@10 {
label = "uImage";
reg = <0x0010 0x0040>;
};

partition@50 {
label = "data";
reg = <0x0050 0x1fb0>;
};
};

KariTanninen


 Minicom Terminal log 
#

Welcome to minicom 2.3

OPTIONS: [18n
Compiled on Feb 26 2009, 00:28:35.
Port /dev/ttyUSB0

 Press CTRL-A Z for help on special keys


=> printenv
baudrate=115200
bootargs=console=ttyS0, 115200n8 
base-installer/initramfs-tools/driver-policy=most
bootargs_console=console=ttyS0, 115200 root=/dev/sdb2 rootdelay=10 
base-installer/initramfs-tools/driver-policy=most
bootcmd=setenv bootargs ${bootargs_console}; run bootcmd_usb; run 
bootcmd_fdt; bootm 0x0080 0x0110 0x0c00;
bootcmd_fdt=fdt addr 0x0c00; fdt resize; fdt chosen; fdt list 
/chosen;
bootcmd_usb=usb start; usb start; ext2load usb 2:1 0x0080 /uImage; 
ext2load usb 2:1 0x0110 /uInitrd; ext2load usb 2:1 0x0c00 /guru

bootdelay=6
eth1addr=F0:AD:4A:00:47:00
ethact=egiga0
ethaddr=F0:AD:4A:00:46:FF
fdt_addr_r=0x0c00
fdt_high=0x
fdtaddr=c00
fileaddr=110
filesize=b2c4af
initrd_high=0x
ipaddr=10.4.50.6
kernel_addr_r=0x0080
ramdisk_addr_r=0x0110
serverip=10.4.50.5
stderr=serial
stdin=serial
stdout=serial

Environment size: 921/131068 bytes
=> tftpboot 0x0080 uImage
Using egiga0 device
TFTP from server 10.4.50.5; our IP address is 10.4.50.6
Filename 'uImage'.
Load address: 0x80
Loading: 
#
 
#

 ###
 4 MiB/s
done
Bytes transferred = 2060842 (1f722a hex)
=> tftpboot 0x0110 uInitrd
Using egiga0 device
TFTP from server 10.4.50.5; our IP address is 10.4.50.6
Filename 'uInitrd'.
Load address: 0x110
Loading: 
#
 
#
 
#
 
#
 
#
 
#
 
#
 
#
 
#
 
#
 
#
 
#

 ###
 3.9 MiB/s
done
Bytes transferred = 11715759 (b2c4af hex)
bootm 0x0080 0x0110
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   Debian kernel
   Created:  2017-12-05  16:25:07 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:2060778 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 0110 ...
   Image Name:   debian-installer ramdisk
   Created:  2017-12-05  16:25:07 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:11715695 Bytes = 11.2 MiB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.





Kari Tanninen kirjoitti 1.3.2018 20:01:

I try tomorrow record Debian "Stretch" U-boot/uImage/uInitrd -terminal
output with instructions
"https://www.cyrius.com/debian/kirkwood/sheevaplug/install/;

Sorry delay, I have to load new binaries to GuruPlug and I'm not very
familiar with unix command line scripting, readable minicom -output
needs little tee/sed processing.

Kari Tanninen


not very handy to make commad line scripting, terminal output

Martin Michlmayr kirjoitti 1.3.2018 15:11:

(Adding Ian Campbell.)

Ok, I didn't notice the version of u-boot from the log you posted and
went on what you wrote.

However,