Query on USB Hub device node creation
Hello Team, I am currently implementing USB Hub support for RX65N target I have a query regarding the device node creation of USB Hub during enumeration process. When USB HID keyboard device is connected, the device node /kbda is created and registered during enumeration. When USB MSC storage device is connected, the device node /sda is created and registered during enumeration. When the USB external hub device is connected, there will be no device node created for USB hub device due to the following reason : usbhost_mkdevname() and register_driver() are not invoked for USB Hub. There will be no entry available in /dev directory for the USB Hub device. Is my understanding correct? Is this the expected behaviour of NuttX? Regards, Anjana Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
Re: Query on USB Hub device node creation
Thank you for the confirmation Regards, Anjana From: Brennan Ashton Sent: 11 September 2020 23:16 To: dev@nuttx.apache.org Subject: Re: Query on USB Hub device node creation **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** On Fri, Sep 11, 2020 at 10:39 AM Schock, Johannes - NIVUS GmbH wrote: > > > There will be no entry available in /dev directory for the USB Hub device. > > > > Is my understanding correct? > > > > Is this the expected behaviour of NuttX? > > I have no hardware around that weekend, so I can't verify. But as far as I > can remember there's no node in /dev for a hub. > > Johannes There was talk at one point of adding support for the /dev/usbN like exists in freeBSD which would also allow for libusb like functionality https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.freebsd.org%2Fcgi%2Fman.cgi%3Fquery%3Dusb%26sektion%3D4%26manpath%3DFreeBSD%2B4.10-RELEASE&data=02%7C01%7CAnjana%40tataelxsi.co.in%7C83981cfb545e4cbe79a408d8567a99aa%7Cad6a39dd96b6436882daf2ec4d92e26a%7C0%7C0%7C637354431864032913&sdata=oVm1f%2FO3fh8Ty%2FwXsug4XpobW%2BpCf3viEltt6yeGz4A%3D&reserved=0 but none of this work has been done --Brennan Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
Implicit declaration warning in RX65N due to ARCH_NOINTC configuration in arch/Kconfig
Hello Team, In arch/Kconfig, for Renesas architecture, the configuration ARCH_NOINTC is selected as mentioned below : config ARCH_RENESAS bool "Renesas" select ARCH_NOINTC select ARCH_HAVE_INTERRUPTSTACK ---help--- Renesas architectures (SH and M16C). Renesas RX65N supports Interrupt controller unit(ICU) and hence ARCH_NOINTC configuration should be disabled. Since it is enabled at the top, we are unable to change the configuration for ARCH_NOINTC . Can we modify this Kconfig to remove "select ARCH_NOINTC" ? Since this configuration is disabled at the top level, the function declarations up_enable_irq() and up_disable_irq() are excluded from the compilation. This results in "implicit declaration" warning for RX65N Regards, Anjana Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
Confirmation for subscription to NuttX mailing list
I confirm to subscribe to NuttX Apache mailing list Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
RTC Periodic interrupt issue
Hello Team, We were testing periodic interrupt for RX65N, and observed that in function rtc_periodic_callback() in rtc.c file, alarminfo->active = false; As per my understanding, alarminfo->active = false;, this will kill the signal, which will disable the interrupt. In effect, periodic interrupt will behave like alarm interrupt. So, alarminfo->active = false; should not be used in rtc_periodic_callback() Please confirm Regards, Anjana Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
NXFLAT Binary loader support for RX65N
Hello Team, I am trying to enable and test NXFLAT binary loader support for RX65N. I have noticed that NXFLAT binary loader requires NXFLAT toolchain to be built using buildroot package. The current NXFLAT toolchain supports ARM targets only. I have referred to https://cwiki.apache.org/confluence/display/NUTTX/NxFlat. What I understand is, in order to support NXFLAT binary loader, the NXFLAT toolchain need to be built using the NuttX buildroot package from https://bitbucket.org/nuttx/buildroot/src/master/ Is there a way by which I can build NXFLAT toolchain for RX65N target? Regards, Anjana Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
ELF Application Example(apps/examples/elf) undefined references issue in symtab.c
Hello Team, I have added ELF Binary Loader support for RX65N target. I am currently testing my implementation using the apps/examples/elf/ example . When I enable the apps/examples/elf/ example application, and compile, I am getting the below error in symtab.c (Symbol Table) C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x14): undefined reference to `_fflush' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x1c): undefined reference to `_fopen' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x24): undefined reference to `_fprintf' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x2c): undefined reference to `_getpid' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x34): undefined reference to `_kill' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x3c): undefined reference to `_longjmp' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x44): undefined reference to `_memset' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x4c): undefined reference to `_nxsched_get_streams' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x54): undefined reference to `_printf' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x5c): undefined reference to `_pthread_attr_init' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x64): undefined reference to `_pthread_create' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x6c): undefined reference to `_pthread_exit' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x74): undefined reference to `_pthread_join' . . The above error is obtained for all the symbols generated in symtab.c from mksymtab.sh. Has anyone faced any similar issue? Any help to resolve the issue would be really helpful. Regards, Anjana Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c
Yes, I have added CELFFLAGS, CELFFLAGS, LDELFFLAGS in Make.defs file From: Ishikawa, Masayuki (SHES) Sent: 18 June 2020 11:33 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** Hi Anjana, Did you add some flags (i.e. CELFFLAGS, CXXELFFLAGS and LDELFFLAGS) to scripts/Make.defs? The flags are needed to build elf modules. Regards, Masayuki 差出人: Anjana 送信日時: 2020年6月18日 14:38 宛先: dev@nuttx.apache.org 件名: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Hello Team, I have added ELF Binary Loader support for RX65N target. I am currently testing my implementation using the apps/examples/elf/ example . When I enable the apps/examples/elf/ example application, and compile, I am getting the below error in symtab.c (Symbol Table) C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x14): undefined reference to `_fflush' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x1c): undefined reference to `_fopen' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x24): undefined reference to `_fprintf' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x2c): undefined reference to `_getpid' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x34): undefined reference to `_kill' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x3c): undefined reference to `_longjmp' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x44): undefined reference to `_memset' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x4c): undefined reference to `_nxsched_get_streams' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x54): undefined reference to `_printf' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x5c): undefined reference to `_pthread_attr_init' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x64): undefined reference to `_pthread_create' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x6c): undefined reference to `_pthread_exit' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x74): undefined reference to `_pthread_join' . . The above error is obtained for all the symbols generated in symtab.c from mksymtab.sh. Has anyone faced any similar issue? Any help to resolve the issue would be really helpful. Regards, Anjana Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this messa
Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c
Hi, I am not working on my github account branch, I am working by downloading the Apache NuttX codebase on my local PC. I was thinking of checking it first on my local PC, and then merging it on github. I have also observed the following, related to the issue observed : 1. I also observed in the apps/examples/elf/tests/mksymtab.sh, it is mentioned that "If the toolchain does any kind of checking for function vs. data objects, then this could fail" 2. As per my understanding, it is possible that since in symtab.c, file all symbols are generated with "_(underscore)", eg: _fflush, _fopen, etc., but since the functions, _fflush, _fopen are not defined(Only fflush, fopen, etc are defined and not _fflush, _fopen), the undefined reference error is coming. 3. Also, In NuttX 8.2 version of code, just to confirm the cause of the issue, I was trying to edit the symtab.c(I understand that it is not right to edit symtab.c, but just to check the cause of the issue), and I replaced _fflush to fflush, and the error of undefined reference was not coming. So, I think, the issue of undefined reference is coming because _fflush, _fopen are actully not defined, only fopen, fflush is defined. So, I think when the compiler tries to map the symbols generated in symtab.c, are looked for Regards, Anjana From: Ishikawa, Masayuki (SHES) Sent: 18 June 2020 12:01 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** Hi, Can you tell us your github account and the branch in which you are currently having trouble so that we can reproduce the errors? Masayuki ________ From: Anjana Sent: Thursday, June 18, 2020 15:23 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Yes, I have added CELFFLAGS, CELFFLAGS, LDELFFLAGS in Make.defs file From: Ishikawa, Masayuki (SHES) Sent: 18 June 2020 11:33 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** ____ Hi Anjana, Did you add some flags (i.e. CELFFLAGS, CXXELFFLAGS and LDELFFLAGS) to scripts/Make.defs? The flags are needed to build elf modules. Regards, Masayuki ____ 差出人: Anjana 送信日時: 2020年6月18日 14:38 宛先: dev@nuttx.apache.org 件名: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Hello Team, I have added ELF Binary Loader support for RX65N target. I am currently testing my implementation using the apps/examples/elf/ example . When I enable the apps/examples/elf/ example application, and compile, I am getting the below error in symtab.c (Symbol Table) C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x14): undefined reference to `_fflush' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x1c): undefined reference to `_fopen' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x24): undefined reference to `_fprintf' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x2c): undefined reference to `_getpid' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x34): undefined reference to `_kill' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x3c): undefined reference to `_longjmp' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x44): undefined reference to `_memset' C:\cygwin64\home\
USB Keyboard device node not removed upon disconnection on RX65N USB Host
Hello Team, We have implemented the USB Host driver for Renesas RX65N target. We are using the keyboard class driver for testing. We have observed the issue mentioned below, upon disconnection of USB Keyboard Issue Observed: 1. When the keyboard device is removed, the device node "/dev/kbd", is not getting removed from /dev directory. 2. Even upon disconnection of USB Keyboard device, the device node still exists. 3. This issue is observed for keyboard device only. When the mass stoarge device is used, this issue is not observed.(Device node for mass storage class, is removed correctly upon disconnection) Has anyone faced similar issue ? Any inputs to resolve the issue will be helpful Regards, Anjana Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
