Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [threadx-dev] Issue with RISCV-64 port causing issues with netxduo
  • From: Bill Lamie <blamie@xxxxxxxxxxx>
  • Date: Mon, 8 Jul 2024 17:17:47 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=px5rtos.com; dmarc=pass action=none header.from=px5rtos.com; dkim=pass header.d=px5rtos.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=nF5NsPsSa8/HULLdCWk0ZzkGILx6E16/B4tr3ZsSDy4=; b=Qp5EG2C95M6QTmOUIT3SB4/LfTlKH0KtUEKKrG5Y93yG7LCjR4YbxTdDRMdIwI6zCXWprIldcdJlKFhWqWa8q/m+gClzluDb/eM6LLK+xeF6yuSRJ2pD1XguEwA0aJPB8qFTFHFd3NGxIi2IjxujV61LUnppyob3GXzbng77SYnUDIchXS1DPgulazHKqKI/llVx/nEpvqoTcYrocpxhcKzvikVsf/c22U0W11ucIeeVQl+HfCHbzVH23ZFfq78UU/no4EegE7ueb6Rhd3EVM3a2cCxqxZCDS2ZbaJIfMD3+RT3p+ZnMzdc0POUwqOEK95d6LyNXepZsH253BhfX+Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Gdc2iPbuL0gSJkjNL6q9duI6TM7s/EUGIZF6vmWBnEgNnFvoVDJye4FQpaWWQLb56qQVa3wpOFtsy5UUqltKeiDs0Kn/KGIanL26Mo+z67ggb+d6MPjSdUncyTPAk48hRNNqc6L5vIRo0Ao1cJbeW32NIaDG5k74Eyml+AbTdS5y4aGj9Vc/3AretpUWOfUt31sX0p3cmSzID00TM2VnKYx0biDG1XfG9tw1+3dFE2kMTjt0KVcEg/wiFj4/OkkA2XH1n/tJliR7hp250usI6/+L5GKJrZRo3Z6ePt8OIfsbpt764evkpC3GCDUvGAS89/HC1RyeIqI8DHNqPhnd0g==
  • Delivered-to: threadx-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/threadx-dev/>
  • List-help: <mailto:threadx-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/threadx-dev>, <mailto:threadx-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/threadx-dev>, <mailto:threadx-dev-request@eclipse.org?subject=unsubscribe>
  • Msip_labels:
  • Thread-index: AQHazt4ALkuojgKUa0ibLE0k7WYIR7HtFhaA
  • Thread-topic: Issue with RISCV-64 port causing issues with netxduo

Hi Adrian,

 

The correct answer is to map ULONG to a 32-bit type in the RISC-V 64-bit port. The entire codebase assumes that ULONG is 32-bits. Changing the RISC-V 64-bit port isn’t as easy as changing types, but the Cortex-Axx 64-bit port should provide a good example. 

 

I hope this helps!

 

Bill

 

 

From: threadx-dev <threadx-dev-bounces@xxxxxxxxxxx> On Behalf Of Adrian SKERRATT via threadx-dev
Sent: Monday, July 8, 2024 6:37 AM
To: ThreadX project developer mailing list <threadx-dev@xxxxxxxxxxx>
Cc: Adrian SKERRATT <askerratt@xxxxxxxxxxx>
Subject: [threadx-dev] Issue with RISCV-64 port causing issues with netxduo

 

Hi All

An issue has been raised on the netxduo repo


For RISCV-64, ULONG is an unsigned long which means it is 64 bits, which causes the netxduo code to fail, but for other 64-bit processors ULONG is a typedef to unsigned int, meaning ULONG is 32 bits.

At first, I thought that means we just needed the RISCV-64 definition to match those of other 64-bit processors, but I'm not sure if the RISCV-64 is implemented differently to x86_64/arm64 due to hardware implementation differences.

Is the correct way to fix this to make ULONG 32 bits on RISCV-64 or to fix the netxduo so that its comparing with a constant rather than sizeof(ULONG) which is implementation dependant?

Adrian

 

Witekio Logo
Adrian Skerratt
Software Engineer
 

 

Witekio UK Limited is a Private Limited Company registered in England and Wales. Registered office: Witekio UK, Units 7 & 8 Brabazon Office Park, Golf Course Lane, Filton, BS34 7PZ. Company number 08178608. VAT number 140658911
This message contains confidential information and is intended only for the individual(s) addressed in the message. If you aren't the named addressee, you should not disseminate, distribute, or copy this e-mail.

We continuously commit to comply with the applicable data protection laws and ensure fair and transparent processing of your personal data. Please read our privacy statement including an information notice and data protection policy for detailed information on our website.

Back to the top